[FEATURE] Routing V2 APIs

[vspecky]

Feature Description

This will serve as the tracking issue for all tasks revolving around all Routing API changes required for Hyperswitch 2.0

Possible Implementation

Tasks

• Refactor Routing endpoints to include descriptive paths and resource IDs wherever required as per guidelines #5050
• Add a status column to the routing_algorithm table to be used for soft deletes #5051
• Add API support for updating a routing algorithm #5052
• Add a column to the business_profiles table for the fallback connector list, and move the same to the new column from the configs table. #5053

Have you spent some time checking if this feature request has been raised before?

• I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit a PR?

No, but I'm happy to collaborate on a PR with someone else