Consider not rebuilding the `breaking-changes.xml` file on each `master` commit

We currently build and deploy the breaking-changes.xml file on each master commit via the breaking-changes-rss-build-and-prod-deploy job (introduced by !121197 (merged)).

Additionally, we have a Generate Breaking Changes RSS Feed pipeline schedule that runs everyday at midnight, which runs the generate-breaking-changes-rss job (introduced by !117316 (merged)).

Both jobs are doing the exact same thing.

I think the pipeline schedule would be enough (effectively removing the breaking-changes-rss-build-and-prod-deploy job) as breaking changes aren't added that often?