[Security Solution] Remove the name field from the security-rule SO mappings

[banderror]

Related to: https://github.com/elastic/security-team/issues/6268 (internal)

Summary

For each of our Saved Object types, we must:

1. Remove any SO field mappings with index: false (or enabled: false, although a first pass was done in Cleanup enabled: false saved objects mappings #149102) from our SO mappings declarations
2. Audit and remove any unused SO fields to minimize our footprint

This PR addresses these two requirements for this security-rule saved object type (prebuilt rule asset).

Details

Specifically, the PR removes the name field from the mappings because:

• We don't filter, sort, search, or aggregate by it.
• We might need to do it in the future for our prebuilt rule upgrade/installation workflows, but for now we're going to implement filtering, sorting, and pagination on the client side, thus there's no need for this mapping server-side.

Also, we may need to add more fields to this mapping in the future to implement further improvements for the prebuilt rule installation, upgrade, or deprecation workflows.

Checklist

• Unit or functional tests were updated or added to match the most common scenarios
  • The unit test for SO mapping hashes has been updated.
  • More tests will be added as part of [Security Solution] Ensure full test coverage for existing workflows of installing and upgrading prebuilt rules #148176 and [Security Solution] Write test plan and add test coverage for the new workflows of installing and upgrading prebuilt rules #148192

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 5f84262

Failed CI Steps

• Security Solution Tests #3

Test Failures

• [job] [logs] Security Solution Tests #3 / timeline flyout button the (+) button popover menu owns focus

Metrics [docs]

Saved Objects .kibana field count

Every field in each saved object type adds overhead to Elasticsearch. Kibana needs to keep the total field count below Elasticsearch's default limit of 1000 fields. Only specify field mappings for the fields you wish to search on or query. See https://www.elastic.co/guide/en/kibana/master/saved-objects-service.html#_mappings

id	before	after	diff
security-rule	4	3	-1

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
securitySolution	433	436	+3

Total ESLint disabled count

id	before	after	diff
securitySolution	513	516	+3

History

• 💔 Build #118246 failed f795b8d9acd9f6e46de706a6dbe537c607389928
• 💔 Build #118082 failed 23fa2d0af41818fa15ad2a19ef83cdaf5b101388

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

cc @banderror

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[afharo]

LGTM