Refactor: Enable Provider Mapping to Accept an Array of Strings for Flexibility with JSON Input

[monilpat]

Is your feature request related to a problem? Please describe.
Currently, providers need to be passed directly into the system, which limits flexibility. It prevents us from dynamically sourcing providers from external .json files or other configurations. This can become cumbersome when managing multiple providers.

---

Describe the solution you'd like
Refactor the current implementation to:

• Create a provider mapping system.
• Allow an array of strings to be passed instead of hardcoding providers directly.
• Dynamically resolve and load providers based on the string array.
• Enable passing in providers from a .json file for improved configurability.

Example:

{
  "providers": ["providerA", "providerB", "providerC"]
}

The system should interpret these strings, map them to their corresponding provider logic, and load them seamlessly.

---

Describe alternatives you've considered

1. Hardcoding providers: This is inflexible and requires manual intervention for every change.
2. Manual parsing of JSON: While possible, this adds unnecessary boilerplate code and duplicates logic that could be centralized.

---

Additional context

• This change improves maintainability and flexibility for managing providers.
• It is especially useful for projects that rely on external configuration files or need runtime provider adjustments.