feat(router): add support v2 /add /retrieve /delete api handler

[ShankarSinghC]

This pr adds the api handler to /add /retrieve and /delete v2 endpoints.
Also adds /fingerprint under v2 that uses the same function as v1 just for the unification purpose .

test case
-> Add data

curl --location 'http://localhost:3030/api/v2/vault/add' \
--header 'x-tenant-id: hyperswitch' \
--header 'Content-Type: application/json' \
--data '{
    "entity_id": "hyperswitch",
    "vault_id": "123456789",
    "data": {
        "card_number": "4111111111111111",
        "name_on_card": "hyperswitch vaut"
    }
}'

{
    "entity_id": "hyperswitch",
    "vault_id": "123456789"
}

-> retrieve data

curl --location 'http://localhost:3030/api/v2/vault/retrieve' \
--header 'x-tenant-id: hyperswitch' \
--header 'Content-Type: application/json' \
--data '{
   "entity_id": "hyperswitch",
    "vault_id": "123456789"
}'

{
    "data": {
        "card_number": "4111111111111111",
        "name_on_card": "hyperswitch vaut"
    }
}

-> delete data

curl --location 'http://localhost:3030/api/v2/vault/delete' \
--header 'x-tenant-id: hyperswitch' \
--header 'Content-Type: application/json' \
--data '{
    "entity_id": "hyperswitch",
    "vault_id": "123456789"
}'

{
    "entity_id": "hyperswitch",
    "vault_id": "123456789"
}

[NishantJoshi00]

Other than that, LGTM

[NishantJoshi00]

what's the _delete_status? can we put a assertion for this to make absolutely sure that the deletion happened?