gh-951 Create DefaultProfileProviderService

[pjmonks]

Interception service responsible for mapping catalogue item hardwired properties to a Profile object and back. This then allows the profile to be applied to other UI controls that require only a profile.

• Map original Mauro profile operations so that a in-memory profile object can be managed
• Create additional helper services to get/set any kind of Mauro item using only minimal identifier information. This circumvents the usual Mauro APIs which require you to know the domain you're working in upfront
• Full test suite provided

Resolves #591

Note: the DefaultProfileProviderService isn't injected anywhere at the moment. Once approved, this is planned to be integrated into the bulk editor in issue #592

[aaronforshaw]

Do you want to include the ReferenceDataModel / Element / Type / Value ?

[pjmonks]

@aaronforshaw Not yet, I probably should have mentioned that in my original PR description. There are a couple of reasons why I wanted to hold off on those:

1. Next iteration of spreadsheet-style bulk editor #576 says that the bulk editor should be improved to include all domain types for Data Models, Terminologies and Code Sets, but Reference Data Models are not included in that yet. As this change is driven by that epic, I wanted to only focus on the essentials first.
2. Issue Unable to edit elements or data in reference data types #69 also discusses updates to the Reference Data Model UI for viewing/editing those domain types, so it kind of feels that Reference Data Models isn't fully supported in mdm-ui fully yet anyway.

Reference Data Models should be included in the future, but that can be a separate issue.

[aaronforshaw]

OK 👍

[aaronforshaw]

Looks good. From memory I think mdm-ui and mdm-explorer have data structures similar to the new MauroIdentifier (although probably they are Data Model specific). Maybe at some point these could be consolidated.

[pjmonks]

@aaronforshaw You're right, in fact there are a lot of components and structures that can be shared between UI projects. I had looked in the past at Angular component libraries to try and create shared reusable components, but hit some roadblocks. It is something that should be reviewed again in the future.

Thanks for the approval 👍