Bump com.fasterxml.jackson.core:jackson-core from 2.13.5 to 2.18.6 in /regression-test/framework

[dependabot]

Bumps com.fasterxml.jackson.core:jackson-core from 2.13.5 to 2.18.6.

Commits

• 9a46ef8 [maven-release-plugin] prepare release jackson-core-2.18.6
• 5f192db Prep for 2.18.6 release
• b0c428e Enforce StreamReadConstraints.maxNumberLength for non-blocking (async) pars...
• 7c8b6d5 Add test for nesting for DataInput-backed JsonParser (#1550)
• 97a647b Update CI: JDK 23 -> 25
• 1601331 (backport from 2.21) Fix #1548: validate max doc length for fixed buffer inpu...
• fae2542 release notes update
• 70c99ba Update UTF8DataInputJsonParser.java (#1512)
• caea665 Post-release dep version bump
• 635d3bd [maven-release-plugin] prepare for next development iteration
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[hello-stephen]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?