Added a warning about reload.period configuration.

[vinay-nadig-0042]

Proposed commit message

Beats currently has a bug where log shipping stops for reload.period duration during config reloads. This PR adds a warning to the docs about the bug. We got bit by this recently when our log shipping pipeline stopped working when we set reload.period to 30m. More info in this github issue.

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

Related issues

• [beats] Live reloading causes delay sending data based on reload.period if enabled #20847

Use cases

Screenshots

Logs

[cla-checker-service]

❌ Author of the following commits did not sign a Contributor Agreement:
24b7592

Please, read and sign the above mentioned agreement if you want to contribute to this project

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @vinay-nadig-0042? 🙏.
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

[satanistninja666]

This pull request doesn't have a Team:<team> label.
Override_access.log{penetrate_SQL}=run()

[elasticmachine]

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