Exclude old aRMT and pRMT versions from catalogue server export

[nivemaham]

Now that we don't have to depend on defining specifications when we add questionnaires, can we keep the latest specification as the default source-type for aRMT and exclude the old versions from being imported on Management Portal.

This will significantly improve the user experience and avoid confusions in future setups

@blootsvoets @mpgxvii @yatharthranjan

[blootsvoets]

That’s a good point. There’s multiple ways to do this:

• Currently, this can be managed via exclude config file. The default should probably be to exclude all but the latest and general specifications.
• removing old versions? I don’t see a major issue with that… the older versions are still available in Git. In fact, perhaps we only need one file per source type. Versioning could still be helpful but the versions will be in git.
• I don’t remember if aRMT relied on a specific version. It would be preferable if not, then it doesn’t matter which version actually gets installed. pRMT does not depend in the version, but it does pick the latest available version.