[Alerting] Exclude security and stack monitoring rule types from rule export.

[ymao1]

Based on discussions about potential duplication of security and stack monitoring rules, we want to filter out these rules types on export.

This depends on #99680. Once that is resolved, we can remove the feature flag for rule import/export and filter out security and stack monitoring rules in the rule onExport hook.

[ymao1]

When this issue is resolved, we need follow-up issues for un-excluding security and stack monitoring rules.

To be able to include security rules in our export, #87992, #99741 need to be resolved.

To be able to include stack monitoring rules in our export, the issues in this meta issue must be resolved.

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[pmuellr]

Would it make any sense to have a rule-type indicate whether it's rules can be exported or not? Default that they can be exported (of course). I have a feeling like we'll end up seeing this again in the future ...

[ymao1]

#99680 has been resolved so this issue is no longer blocked.

[ymao1]

When this issue is resolved, we need follow-up issues for un-excluding security and stack monitoring rules.

To be able to include security rules in our export, #87992, #99741 need to be resolved.

To be able to include stack monitoring rules in our export, the issues in this meta issue must be resolved.

Followup issues:

• [Alerting] Include security rules in import/export #103600
• [Alerting] Include stack monitoring rules in import/export #103599