Allow external sources to have their derivation group changed

[JosephVolosin]

• Tickets addressed: N/A
• Review: By commit
• Merge strategy: Merge (no squash)

Description

This PR updates the Hasura metadata for external_source to allow derivation_group_name to be changed - allowing sources to have the derivation group they belong to changed after upload (previously, the group was locked in at the time of upload).

The potential downside of this change is that moving a source out of a derivation group that is currently tied to a plan will not provide any notification to the user that a source they may expect to be part of the plan is not longer part of the plan because it's derivation group was changed. The UI PR attempts to alleviate this by providing the user a warning if they are changing a source from a derivation group that is currently used by any plan(s).

This change should help allow more flexibility with derivation groups. Currently the process to change a derivation group is to delete the source and re-upload it with the new derivation group name, this also includes dis-associating the original derivation group from all plans its tied to prior to deleting the source and then re-associating the group afterwards.

Verification

Via. Hasura and UI PR

Documentation

aerie-docs should be updated to reflect this option

Future work

N/A

[Mythicaeda]

This permission should have the same filter as in delete, rather than letting any user with the user role change it. (The delete permission says that only the owner of the source OR the owner of the derivation group the source is in can modify the source)