feat(weaver): revisit COPM organization configuration interfaces

[jenniferlianne]

Is your feature request related to a problem? Please describe.

Following from the discussion here: #3625 (comment) the weaver team will revisit the configuration interfaces for the copm module.

I suggest that this happen as part of a product management effort that considers the full weaver system configuration, with analysis and documentation of the user story maps for:

• setting up a new organization
• adding a new asset type for transfer or exchange
• removing an asset type for transfer or exchange
• removing an organization

This should include a definition of the roles who will be involved as well as key parameters such as:

• the maximum number of supported organizations
• the maximum number of asset contracts that can be transferred or exchanged
• traceability requirements for who has made changes to the configuration and when (eg. support for ALCOA standards)

As this will drive the technical choices.