Document havester_limit for Filestream input and fix typo

[belimawr]

Proposed commit message

This commit documents harvester_limit for the filestream input and replaces close_* by the correct key close.on_state_change.*.

Checklist

• ~~[ ] My code follows the style guidelines of this project~~
• ~~[ ] I have commented my code, particularly in hard-to-understand areas~~
• [x] I have made corresponding changes to the documentation
• ~~[ ] I have made corresponding change to the default configuration files~~
• ~~[ ] I have added tests that prove my fix is effective or that my feature works~~
• ~~[ ] I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.~~

~~## Author's Checklist~~ ~~## How to test this PR locally~~

Related issues

• Closes https://github.com/elastic/beats/issues/38784

~~## Use cases~~ ~~## Screenshots~~ ~~## Logs~~

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[mergify[bot]]

This pull request does not have a backport label. If this is a bug or security fix, could you label this PR @belimawr? 🙏. For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2024-04-26T20:56:27.276+0000

• Duration: 11 min 50 sec

:grey_exclamation: Flaky test report

No test was executed to be analysed.

:robot: GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)