Backport PR #16882 to 8.17: Validate the size limit in BufferedTokenizer.

[github-actions]

Backport PR #16882 to 8.17 branch, original message:

---

Release notes

[rn:skip]

What does this PR do?

Currently, BufferedTokenizer doesn't validate size limit. That means any negative or zero value can lead input buffer full exception. This PR adds a safeguard validation on size limit to allow only positive number.

Why is it important/What is the impact to the user?

As it is a public interface, this enhancement improves interface experience.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files (and/or docker env variables)
• I have added tests that prove my fix is effective or that my feature works

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Closes Add the ability to disable verification by creating the BufferedTokenizer with 0 bytes. #16824

Use cases

Screenshots

Logs

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 9f98a26

[mashhurs]

lgtm