Improve provider selection logic in Config.get_provider_for method

[lenage]

Description

This PR enhances the get_provider_for method in the Config class to provide more accurate and efficient provider selection. The updated implementation prioritizes exact matches and then selects the most specific subclass when dealing with inheritance hierarchies.

Changes

• Modified get_provider_for method to first check for an exact match between the client type and available providers.
• If no exact match is found, the method now identifies all matching providers based on subclass relationships.
• Implemented a sorting mechanism to select the most specific (derived) provider when multiple matches are found.

Testing

create a new ProviderClass which is a subclass of OpenAIProvider

class AwesomeProvider(OpenAIProvider):
    def translate_to_provider(self, ell_call: EllCallParams) -> Dict[str, Any]:
         #make some changes

    def translate_from_provider(self,
                                provider_response,
                                ell_call: EllCallParams,
                                provider_call_params: Dict[str, Any],
                                origin_id: str | None = None,
                                logger: Callable[..., None] | None = None) -> Tuple[List[Message] | Dict[str, Any]]:
        return super().translate_from_provider(provider_response, ell_call, provider_call_params, origin_id, logger)

ell.register_provider(AwesomeProvider())

then, if you call ell.simple, it always use OpenAIProvider instead of AwesomeProvider
This PR fix above issue to check inheritance hierarchies

Additional Notes

This change maintains backwards compatibility while providing more precise provider selection, especially in cases involving complex inheritance hierarchies.

[MadcowD]

I'll take a quick look

[MadcowD]

Would you be willing to add a few tests for this PR?

[MadcowD]

Ready to merge just dont want to have regressions in the future

[lenage]

Would you be willing to add a few tests for this PR?

sure, will add some test soon

[lenage]

Would you be willing to add a few tests for this PR?

sure, will add some test soon

@MadcowD tests added

[lenage]

@MadcowD have a sec to check this out?

[MadcowD]

Can you add an assertion error or a Warnung if there are two mstching providers of the same mro lehnte