Use llama_stack_api instead of llama_stack.api

[leseb]

Llama Stack recently moved the API definitions and datatypes in a separate package llama_stack_api. So all imports should use llama_stack_api instead of llama_stack.api.

We are working on publishing llama_stack_api as a package too. It's not 100% needed the provider always runs next to llama-stack which brings llama_stack_api with it. But it's likely useful for your testing.

[leseb]

cc @cdoern

[cdoern]

It's not 100% needed the provider always runs next to llama-stack which brings llama_stack_api with it. But it's likely useful for your testing.

this is true, but switching to llama_stack_api is important because it'll allow us to potentially use different versions of the API with different llama stack versions.

currently if the provider pins llama_stack==0.2.3 but we want to ship llama_stack==0.4.0, we hit a whole bunch of issues and dependency overrides when installing providers!

[m-misiura]

Thanks @leseb and @cdoern -- there is work on this branch: https://github.com/m-misiura/llama-stack-provider-trustyai-fms/tree/migrate-to-llama-stack-api

A PR should follow soon