Different token IDs for different projects by the same policy

[anvabr]

Problem description

It is common to allow an undetermined/unlimited number of different projects to be created/registered under the same Guardian policy (methodology). For these projects, their respective project developers can submit PDDs and other data via forms, resulting in a production of the trust chain of various VC/VP documents and ultimately in the minting of tokens. However, there is currently no way to differentiate (except for the metadata) between the tokens 'belonging' to different projects (run by different project developers), as all tokens issued by such policy would have the same TokenID.

Requirements

• Introduce the facility to dynamically create new TokenIDs and 'assign' them to (newly registered) specific projects such that all data associated with these specific projects would be linked to the corresponding TokenIDs upon minting instances of the token.
• Ensure clear association with the same methodology for all TokenIDs and their respective trustchains. I.e. it should be clear that 'these tokens' have been issued by the same Policy, but for different projects.
• Extend trust chain to show multiple tokens and multiple projects 'managed' by the same policy

Definition of done

• New functionality fulfils requirements specified above
• Documentation extended/updated accordingly
• An example usage of multi-token facility is implemented in at least one of the Guardian policies in the repository

Acceptance criteria

• Policy authors are able to create policies implementing the multi-token concept
• Trust chain, project data search and comparison, and other Guardian UI pages (such as various grids) support the multi-token concept by correctly displaying associations between multiple created token IDs and a single policy