Deprecate Rules V1 Standard

[AndyRae]

Is this the right issue type?

• Yes, I'm planning work for this project team.

Summary

As referred to in: #1276

As the GUI will change, it would then be creating concepts which are not supported by V1.
So I think we should start a decent deprecation process across V1.

including a warning when those rules are requested and downloaded
and then when they are used in Carrot Transform

This should start with a warning, and then when we meet a satisfied time period (no V1 rules being generated?), and/or it is limiting development, we can remove the functionality.

I do not think this requires a breaking change release for Mapper, as this is about support for a rules standard, not a breaking change to this software. But happy to take opinions.

This can also form the basis of not using V1/V2 terminology, and that there is just the "Carrot Mapping Standard"

Acceptance Criteria

• Warning added when requesting rules V1
• Warning added when downloading rules V1
• Remove ability to request V1 files
• Rename any V2 UI to just "Mapping Rules"

Confirm creation

• Ready to create this feature?