updating rule names to match current

[kgeller]

What does this PR do?

This updates the filter for two lens visualizations on the dashboard to use the current rule names.

In 8.8 we deprecated the existing rules in favor of new, more specific names. This change was then backported to 8.5. So, this PR updates those names and sets the min version to 8.5

For more context, see https://elastic.slack.com/archives/C02TNUE3P6F/p1688126475454089

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

How to test this PR locally

Related issues

Screenshots

[elasticmachine]

💚 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: 2023-07-12T18:56:53.249+0000

• Duration: 14 min 53 sec

Test stats 🧪

Test	Results
Failed	0
Passed	2
Skipped	0
Total	2

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[bhapas]

Can we add some screenshots to provide context for public users

[kgeller]

@bhapas

Can we add some screenshots to provide context for public users

There already is one, and it doesn't change with this PR. It just gets fixed since the rule names have been updated

[elasticmachine]

Package ti_util - 1.2.2 containing this change is available at https://epr.elastic.co/search?package=ti_util