Enhance the container family validation for multi-model deployment

[mrDzurb]

Description

This PR introduces support for relaxing container family validation in multi-model deployment by incorporating container family compatibility rules.

Enhancements:

• Introduced CONTAINER_FAMILY_COMPATIBILITY map, which defines compatible container families and preferred family when multiple compatible types are detected.
  • Example: "odsc-vllm-serving" and "odsc-vllm-serving-v1" are now treated as compatible; "odsc-vllm-serving-v1" is preferred.
• Updated model validation logic to:
  • Detect when all models belong to compatible families.
  • Automatically select the preferred container family for deployment.
  • Raise errors when incompatible or missing families are found.

Added:

• Utility function: get_preferred_compatible_family(...)
  • Returns the best-suited family from a list based on the compatibility map.
• Unit tests for get_preferred_compatible_family.

[kumar-shivam-ranjan]

Is there specific reason why we have chosen odsc-vllm-v1 as key and not odsc-vllm?
If i understand correctly , if 2 or more models are chosen with some models compatible with odsc-vllm-v1 and others with odsc-vllm, the group will be deployed with odsc-vllm-v1. and if all selected models are compatible with odsc-vllm , we still go ahead and deploy with odsc-vllm-v1?
Correct me if am wrong. @mrDzurb

[kumar-shivam-ranjan]

I see.
I believe odsc-vllm-v1 is preferred in both the cases.

[mrDzurb]

There is no perfect solution for this, in my opinion. Ideally, we would re-test all service models and update them to use the latest container, but that would be too time consuming. For now, this is just a best-effort attempt to choose the most recent container family when models from different families are mixed. Hopefully, VLLM will continue to improve, and the enhancement introduced in this PR will be more robust.

[github-actions]

📌 Cov diff with main:

📌 Overall coverage:

[VipulMascarenhas]

nit: use -> Optional[str] instead of str.