[9.x][Filebeat] add known issue entries about Filestream clean_inactive

[belimawr]

Proposed commit message

See title

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
• 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.

## Disruptive User Impact
## Author's Checklist

How to test this PR locally

Build the docs, navigate to http://localhost:3000/release-notes/known-issues

Related issues

• Filestream reingests data when clean_inactive is set #45601

## Use cases
## Screenshots
## Logs

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

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

[elasticmachine]

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

[github-actions]

🔍 Preview links for changed docs

• docs/release-notes/known-issues.md

[colleenmcginnis]

Left a couple minor suggestions below.

[colleenmcginnis]

Is there an issue and/or PR we can link to? Something like... For more information, refer to [issue #](issue link).

[belimawr]

Yes and no.

There is the issue/task: #45601, but I don't believe it is very helpful for users to read it.

The PR (#46373) adding it does not contain much details about the issue, it's more about the fix.

[colleenmcginnis]

Is there an issue/PR you can link to here, too?

[belimawr]

The same thing as #46392 (comment)

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b 45601-clean-inactive-known-issues-main upstream/45601-clean-inactive-known-issues-main
git merge upstream/main
git push upstream 45601-clean-inactive-known-issues-main

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b 45601-clean-inactive-known-issues-main upstream/45601-clean-inactive-known-issues-main
git merge upstream/main
git push upstream 45601-clean-inactive-known-issues-main

[colleenmcginnis]

If we're backporting to 9.1, I wonder if we should hold off on adding this line or reframe to something like this until the release:

Suggested change

	**Fixed in**: 9.2.0
	**Fix planned in**: 9.2.0

This is where it might be helpful to link to the PR that fixes it so if the user is in doubt and particularly interested in this issue, they can check the changelog as a source of truth. I'll leave it up to you, and I won't block this PR from being merged.