wiz.issue: Remove deprecated source_rule field

[kcreddy]

Proposed commit message

wiz.issue: Remove deprecated "source_rule" field

This is 3rd and final part of #16627 where the deprecated 
"source_rule" field is removed from the "issue" data stream. 
The new "source_rules" field is already added in #16692.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Related issues

• Relates [WIZ]: Support new graphQL sourceRules node and remove deprecated sourceRule node query and add risks. #16627

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[StacieClark-Elastic]

Thank you for this work.
One of the concerns with this deprecation is whether there are dashboards or rules written by other teams that rely on this field. The dashboards that are in the integration do not rely on it but there are concerns that there are other artifacts out of our control that might rely on it. For instance, the customer that created the SDH has written some rules that rely on it.
A longer description describing the change and what the impact on the customer is and how to mitigate the impact would be helpful so they don't have to read through the entire changelog to understand that we added a replacement field.

[kcreddy]

Thank you for this work. One of the concerns with this deprecation is whether there are dashboards or rules written by other teams that rely on this field. The dashboards that are in the integration do not rely on it but there are concerns that there are other artifacts out of our control that might rely on it. For instance, the customer that created the SDH has written some rules that rely on it. A longer description describing the change and what the impact on the customer is and how to mitigate the impact would be helpful so they don't have to read through the entire changelog to understand that we added a replacement field.

@StacieClark-Elastic, I updated the changelog description to add more details. PTAL.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: bce355a

History

• 💚 Build #36174 succeeded ec11398

cc @kcreddy