Add possibility to update threat_indicator_path for prebuilt rule

[nkhristinin]

Add the possibility to update threat_indicator_path for the prebuilt rule.

How to reproduce the bug:

We will update this file -x-pack/plugins/security_solution/server/lib/detection_engine/rules/prepackaged_rules/threat_intel_module_match.json

• checkout master branch
• install all prebuilt rules
• open the Threat Intel Filebeat Module Indicator Match
• check that in the network panel the request for this rule has threat_indicator_pathequals ""
• change threat_indicator_path to any value
• increase the version
• save file
• you should see this button

• update rules
• check Indicator math rule again in the network request
• threat_indicator_pathshould be the empty string - ""

Check out branch

• Go to x-pack/plugins/security_solution/server/lib/detection_engine/rules/prepackaged_rules/threat_intel_module_match.json
• change threat_indicator_path to any value
• increase the version
• you should see this button

• update rules
• check Threat Intel Filebeat Module Indicator Match rule again in the network request
• threat_indicator_pathshould has a value which you enter before

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[nkhristinin]

@elasticmachine merge upstream

[elasticmachine]

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

[rylnd]

Great catch, I missed these paths in #91260.

In order to ensure we don't introduce a regression here, it would be great to add some test coverage in update_prepacked_rules.test.ts, verifying that modification of some representative fields (including threat_indicator_path) are persisted by that function.

[ecezalp]

@elasticmachine merge upstream

[ecezalp]

LGTM - making a note of the update_prepackaged_rules.test.ts in the testing doc here for 8.0

[ecezalp]

@elasticmachine merge upstream

[ecezalp]

@elasticmachine merge upstream

[elasticmachine]

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

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 1c4f276
• Storybooks Preview

Metrics [docs]

✅ unchanged

History

• 💚 Build #9037 succeeded b42844e
• 💚 Build #7021 succeeded 0139b90
• 💚 Build #2658 succeeded 0ecc745
• 💔 Build #2466 failed a8c72dfc906eca14e86f17cad8755ba5d5b3cb69
• 💔 Build #2405 failed 4d788ea09ebddf0338a53caa6c7d725b1d0808e3

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

cc @nkhristinin

[kibanamachine]

The following labels were identified as gaps in your version labels and will be added automatically:

• v8.1.0

If any of these should not be on your pull request, please manually remove them.

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	8.0

This backport PR will be merged automatically after passing CI.