Cloudwatch Logs: Clarify Cloudwatch Logs Limits

[sarahzinger]

What is this feature?

• notifies users that they can only query 50 log groups at a time

• clarifies what cloudwatch logs time out is about

Why do we need this feature?

• It was unclear to users that they could only query 50 log groups at a time
• It was unclear to users what the cloudwatch log timeout does, as there is a separate but unrelated cloudwatch logs timeout that is up to 60 minutes and not configurable: In reality this timeout is referring to a retry limit that we do after hitting concurrency errors (CloudWatch Logs: Add retry strategy for hitting max concurrent queries #39290)

Who is this feature for?
Cloudwatch Logs users

Which issue(s) does this PR fix?:

Fixes #64336
Fixes #65471

Special notes for your reviewer:

Please check that:

• It works as expected from a user's perspective.
• If this is a pre-GA feature, it is behind a feature toggle.
• The docs are updated, and if this is a notable improvement, it's added to our What's New doc.

[grafanabot]

Hello @sarahzinger!
Backport pull requests need to be either:

• Pull requests which address bugs,
• Urgent fixes which need product approval, in order to get merged,
• Docs changes.

Please, if the current pull request addresses a bug fix, label it with the type/bug label.
If it already has the product approval, please add the product-approved label. For docs changes, please add the type/docs label.
If the pull request modifies CI behaviour, please add the type/ci label.
If none of the above applies, please consider removing the backport label and target the next major/minor release.
Thanks!

[github-actions]

Backend code coverage report for PR #67072
No changes

[github-actions]

Frontend code coverage report for PR #67072

Plugin	Main	PR	Difference
cloudwatch	83.03%	83.03%	0%

[iwysiu]

Nice! Lgtm