[Feature] Launch V2 APIs

[tinu-hareesswar]

The issue serves as the tracking issue of version 2 of Hyperswitch Card Vault.

What's new:

• Hyperswitch aims to be a generic storage vault agnostic of payments domain constraints.
• Having the to flexibility to suit all tenant application use cases
• Support for multi-tenancy with logical separation of data
• Updates to be compliant with the new PCI DSS 4.0 certification
• Adding support for secret store for key management

Implementation

Multi-tenancy

• Logical separation of database for each tenant
• Custodian Autonomy for each tenant to be unlocked by their custodian #99
• Implement schema based multi-tenancy for DB connections #98
• Implement middleware for constructing app-state based on request context #100

Generalisation

• Hyperswitch application changes to make it compatible with V2
• Support for TLS encryption #104
• Rewriting API contracts to make it generic for flexibility in tenant use cases

Key Management

• Move crypto related managers to separate modules #96
• Integrating a secret manager #109
• Api endpoint for migration of keys to secret manager #113
• Setting up policies for key rotation

Misc

• Record tenant_id header field in request trace #102
• Remove tenant_id column from all existing tables #106
• Add db migrations for v2 #108