feat(platform): KYC flow design - defer to provider

[betimshahini]

To frame the ideation of the KYC support we'd like to add, we want to design a ideal-case set of flows, that incorporate assumed integration patterns with KYC providers.

There are two high-level flows:

• The developer configuration and APIs where a developer enables and configures the KYC provider and any settings they require. The design of the APIs and integration patterns are out of scope for this ticket.
• The end-user experience, to cover initiation of an external KYC process (to create a KYC data package) and one to consent sharing an existing KYC data package with a particular application through our authorization screen. This can follow a similar pattern to adding a new OAuth connected account through the authorization screen.

Task tracks:

• [ ] UX design in Figma for developer and for end-users.

[picassobanana]

*Design in not final and should be revisited once we have more complete requirements

Figma Link

Developer Configuration:

Passport - Auth Sreen

Passport - Platform