[Release 3.0] Planned Breaking Changes for 3.0 in Plugin

[peterzhuamazon]

[Release 3.0] Planned Breaking Changes for 3.0 in Plugin

As mentioned in this META Issue, we want to track and increase transparency around the breaking changes planned for the 3.0 release across participating plugins.

Please kindly document all planned breaking changes related to your plugin for 3.0 here, by sharing detailed information about the changes, expected impact, and any guidance for users or other teams to adapt to the changes.

If needed, please also prepare PRs on documentation-website changes as part of the 3.0 release process.

Overall, this would help us deliver a smooth and seamless upgrade experience.

Thanks.

[andrross]

Catch All Triage - 1, 2, 3, 4, 5

[AWSHurneyt]

1. As mentioned in Remove Alerting destinations concept and destination migrator for OpenSearch 3.0 #1781, destinations-related assets should be deprecated from the back, and frontend plugins
   1. Common utils has some destinations legacy assets to deprecate
2. As mentioned in [Release 3.0] Planned Breaking Changes for 3.0 in Plugin alerting#1769 (comment), the job scheduler functionality of the alerting plugin should be deprecated, and it should instead integrate with the job scheduler plugin. Since the alerting plugin has a dependency on common utils, we should be mindful of any common utils changes needed to support the new integration
   1. Depending on the 3.0 release timeline, this may be out of scope
   2. Note: common utils may not actually need any changes to accommodate this

[AWSHurneyt]

Per @Murali-Arigala, we will not be making any breaking changes for 3.0.