[ResponseOps][Rules] Map rule actions params as flattened to allow search

[umbopepato]

📄 Summary

• Maps the rule (once called alert) SO actions.params field as flattened to allow searching by action params

Important

This currently only supports searching by actions.params as a whole (i.e. in all leaf values of the params object). Support for deeply nested search (actions.params.param) will be added in a separate PR

🧪 Verification steps

1. Create one or more rules with actions (i.e. email)
2. From the devtools, run the rules find API searching by any action param value:

GET kbn:/api/alerting/rules/_find?search=youractionparamvaluehere&search_fields=actions.params

3. Check that the search results match your search criteria

⏪ Backport rationale

Not backporting since this is an enhancement

🔗 References

Closes https://github.com/elastic/response-ops-team/issues/339

Release Notes

Adds support for searching rules by their actions' params via API

☑️ Checklist

• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
• Flaky Test Runner was used on any tests changed
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
• Review the backport guidelines and apply applicable backport:* labels.

[elasticmachine]

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

[cnasikas]

LGMT!

[umbopepato]

Re. this: we're not adding any new SO fields, just adding mappings for the pre-existing actions.params property so I added fixtures with two identical rules, specifying actions unlike we did for the last migration file that was created for rules

[cnasikas]

@elasticmachine merge upstream

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: d8c14cd

Failed CI Steps

• Scout: [ platform / streams_app ] plugin

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
alerting	833	835	+2

Page load bundle

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

id	before	after	diff
alerting	24.2KB	24.2KB	+26.0B

Unknown metric groups

API count

id	before	after	diff
alerting	872	874	+2

History

• 💛 Build #372600 was flaky 708d08f
• 💔 Build #372468 failed 2d0f41c
• 💔 Build #372351 failed eaa6c10
• 💔 Build #372338 failed 2d3e57d
• 💔 Build #372287 failed a189df7