LLMConsumptionRegistry

Resolves consumption flavors discovered on the classpath via LLMConsumptionType services.

Discovery is lazy (on first use) and uses the thread context classloader, so there is no startup-ordering requirement: whichever provider jars are present contribute their flavors. The library ships LiteLLM; the consuming app contributes its own provider-specific flavors via its own META-INF/services entry.