Refactor: Unify Chat Completion Interface

[Kirti-Rathi]

Multiple API providers follow the same chat completion structure. However, the logic is duplicated across implementations. This violates the DRY principle and increases maintenance overhead.

---

Acceptance Criteria:

• All supported providers follow a unified structure for chat completions
• Duplicate code patterns across providers are eliminated
• Existing functionality and behavior remain unchanged
• Backwards Compatibility: Provider-specific variations (Existing behavior for model, max_tokens, temperature, and other defaults) are preserved where needed
• Codebase is easier to maintain and extend

[mehakmander11]

hii @Kirti-Rathi could u assign me this issue please, i will start working 14th onwards

[Kirti-Rathi]

Assigned!
Feel free to reach out if you've any doubts.

[Alam9835]

@Kirti-Rathi wanna work on this issue.

[Kirti-Rathi]

@Alam9835 Assigned.
Better PR will get merged

[Kirti-Rathi]

@mehakmander11 @Alam9835 It's been close to 10 days since the issue was assigned to you, but no PR has been raised yet. Pls share an update or let me know if you need help.

[GxAditya]

@Kirti-Rathi can you assign me this issue if it is available under ssoc 2025?