Provide a way to fix orphaned triggers in Bamboo for regular (non-Specs) build plans

Issue Summary

This affects Data Center:

It would be nice if Bamboo could automatically search for & remove orphaned plan triggers OR provide a way to do this in bulk. At the moment the only way to fix an orphaned trigger for a plan that is not managed by Bamboo Specs is to open up the Default plan configuration > Triggers tab, locate the trigger and re-save it. This is not something realistic to do if it's affecting hundreds of different plans.

Orphaned triggers don't seem to cause any problems but Bamboo will constantly report them in the logs with the following messages:

2022-11-23 15:19:42,658 INFO [scheduler_Worker-8] [StashTriggerQuartzJob] Triggerable: CHAIN:PROJ-PLAN; Found triggering repositories that are no longer in chain definition (repositories: [950261])
2022-11-23 15:20:03,921 INFO [scheduler_Worker-7] [StashTriggerQuartzJob] Triggerable: CHAIN:PROJ-PLAN0; Found triggering repositories that are no longer in chain definition (repositories: [950261])
2022-11-23 15:20:34,311 INFO [scheduler_Worker-6] [StashTriggerQuartzJob] Triggerable: CHAIN:PROJ-PLAN1; Found triggering repositories that are no longer in chain definition (repositories: [950261])

With time this might start polluting the application logs and depending on how many plans (and plan branches) are affected by this problem it will start affecting people's ability to effectively read the application logs.

Workaround

Regular (non-Specs) build plan(s)

1. Take note of the key from the affected plan (from the example above: PROJ-PLAN).
   • It's not necessary to go through the following steps for the branches of a plan, only the main plan branch (unless the affected plan branch was configured to override the triggers set for the main plan branch).
2. Access the $BAMBOO_BASE_URL/chain/admin/config/editChainTriggers.action?buildKey=$planKey page.
   • Replace $planKey with the key from the affected plan from step 1 (e.g. PROJ-PLAN).
3. Re-save the trigger(s) inside the page.
4. You should no longer see "Found triggering repositories that are no longer in chain definition" messages inside the application logs for this plan and its plan branches.