feat(platform): Create API authorization data patterns based on Persona

[betimshahini]

With the authorization values now being selectable by the user, the API data patterns (read, write) need to take into account the selected entries in the Persona. Eg. an operation with the email scope at the API level should only have access to the selected email; an operation against connected addresses should only be performed to the selected connected addresses.

Currently, the logic is based on scope alone; this needs to be enhanced to take into account the values authorized within that scope.

Tracks:

• [ ] Design of pattern
• [ ] Implementation of at least one use case.