Request KYC endpoint

[Filip-L]

Endpoint: verifier/application/request_kyc

Description:
The functionality enables Allocators to request their clients to undergo the KYC process.

The verifier/application/request_kyc endpoint checks, based on the data received (KYCRequestedInfo), the current state of the application. If the condition is met, it:

• Updates the application's state to KYC requested.
• Updates the record in the database.
• Adds a comment on relevant GitHub issue and the label to kyc requested.
• Creates a commit with the updated application state on relevant branch.

Usage Condition:
To execute this endpoint, the following conditions must be met:

1. The application must be in the Submitted state.

Deployment Considerations:

• new environment variable KYC_URL - variable should be set to the URL of the KYC portal

Example KYCRequestedInfo:

{
  "id": "client_address",
  "owner": "owner_name",
  "repo": "repo_name"
}

[kacperzuk-neti]

There're more places where we need to handle the new state.

In fplus-lib/src/core/mod.rs, line 835, in complete_governance_review, there's a whitelist of states for which complete_governance_review can be triggered. Right now that's Submitted, AdditionalInfoRequired and AdditionalInfoSubmitted. We should add the new KYCRequested to it, so that allocator can override it if needed.

In fplus-lib/src/core/mod.rs, line 1711, we're validating the flow (read-only endpoint it seems) (part of GH Action: https://github.com/fidlabs/allocator-template/blob/main/.github/workflows/flow-validator.yml ). We should probably consider it invalid if we're in KYCRequested, but we do have current allocations.

[kacperzuk-neti]

Superseded by #195