[RAM] Fix filtering tags by special characters

[JiaweiWu]

Summary

Resolves: #135599

Fixes the inability to filter on tags with special characters

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[cnasikas]

I am not sure if it is relevant to the PR but you can use escapeKuery from @kbn/es-query

[JiaweiWu]

I tried to use escapeKuery but it seems like that does not escape {}. Looking at the source code, it does seem to support that assumption.

function escapeSpecialCharacters(str: string) {
  return str.replace(/[\\():<>"*]/g, '\\$&'); // $& means the whole matched string
}

Also I noticed this regex pattern is used in security solutions: x-pack/plugins/security_solution/public/management/common/utils.ts. But yes I do think it would be ideal if we can just use the same regex across the code base. So I wouldn't mind just using escapeKuery

[XavierM]

@elasticmachine merge upstream

[jcger]

👏

[JiaweiWu]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: e810424
• Storybooks Preview
• Cloud Deployment

Metrics [docs]

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
triggersActionsUi	89.6KB	89.7KB	+55.0B

History

• 💔 Build #56723 failed 8a0d922
• 💔 Build #55132 failed aecc065

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[JiaweiWu]

fixed by this pr: #136312