Combine ansible-collection-infra & UCLMedicalImagingEnv configs

[paddyroddy]

In order to reduce repetition and have a single source of truth, I have looked through all repos and found the only ansible-collection-infra and UCLMedicalImagingEnv have custom configs that make sense to reuse — for example, combining XNAT plugins. This PR is preliminary work before I investigate minimumReleaseAge.

Once this is merged, I will raise PRs in the respective repos to simplify their configs.

[p-j-smith]

nice to remove some duplication!

Is it worth putting these changes into a separate config in this repo (e.g. xnat-config.json5) that the collection and and UCLMedicalImagingEnv can use, so that other repos don't have these unnecessary datasources and package rules?

I don't feel strongly about this though. Happy with whatever you decide

[paddyroddy]

Is it worth putting these changes into a separate config in this repo (e.g. xnat-config.json5) that the collection and and UCLMedicalImagingEnv can use, so that other repos don't have these unnecessary datasources and package rules?

My thought is that we would always want those XNAT plugins combined etc., so I'd be inclined to disagree. Any thoughts @drmatthews @HChughtai?

[p-j-smith]

My thought is that we would always want those XNAT plugins combined etc.,

Yep that's true, although I was thinking more about repos that don't have XNAT and these plugins as dependencies. Not super important though, happy for it to stay in the default config

[paddyroddy]

Yep that's true, although I was thinking more about repos that don't have XNAT and these plugins as dependencies. Not super important though, happy for it to stay in the default config

Essentially, nothing would happen. It would find dependencies, check if they're in a group, do something. In this case it wouldn't find anything and then move on.

[paddyroddy]

Have discussed with Haroon and these are sufficiently general that I am going to merge.