Ability to "Group" Activities Linked via Scheduling

Checked for duplicates

Yes - I've already checked

Alternatives considered

No - I haven't considered

Related problems

This is somewhat related to the issue found with the activityFinder (https://github.com/NASA-AMMOS/aerie/issues/1061). If the ability to group scheduled activity instances and space them out from other distinct groupings was available this activityFinder bug would be a more minor problem.

Describe the feature request

When scheduling groupings of activity instances together it would be helpful to have the option to prevent that "group" from overlapping with other "groups" (via group mutexes or a new global scheduling condition). There are many instances where one scheduling goal sets up GNC turns and array articulations surrounding a primary instrument activity instance. When setting these up in a larger plan, in many cases we want these groupings to not overlap with other goal's groupings that involved GNC/array articulations.

Currently, mutexes can be written to prevent overlap of the GNC and array activity types, but it would be beneficial to have the capability to write mutexes preventing overlap of scheduled groupings of activity instances relative to one another. Similarly, being able to set spacing preferences between scheduled groupings would aide significantly in planning (i.e. allow 30 minutes on either end of X grouping from other groupings). This could potentially be handled with a global scheduling condition and would help break up spacing of linked activities in the plan.

A workaround that was put in place to build Clipper's Thread Test 6 plan was to shift the applyWhen window for select anchor activity placements to X hrs after a notable event (in TT6 the >2AU transition) instead of leaving the goal with simply the true constraint (>2AU). This was to space out the scheduled activity groupings to fall in a more logical ordering along with buffer time in between groups.