Support AWS Bedrock as an Assistant provider

[aus]

Check for existing issues

• Completed

Describe the feature

Add AWS Bedrock as an Assistant provider.

If applicable, add mockups / screenshots to help present your vision of the feature

No response

[KoStard]

Looking forward to this!

[CrazyFunker]

I would be very excited for this feature! It would enable us to push for and recommend using Zed at my company!

[5herlocked]

I would like to take this on; however, I would need guidance on how/what integration points we'd need to curate for Zed.

[5herlocked]

I've started working with this and with Bedrock's model list getting longer each quarter, I thought a procedural macro might be the way to go when making the list of models. That way each build gets the most up-to-date Bedrock model without having to curate it letting the user pick the best model for their purpose.

Does Zed have a particular policy for or against proc_macros?

For the extension itself, I'm going to try and follow the Anthropic crate but instead of HTTP requests, I'll use the AWS Bedrock Runtime Client.
For auth, I'll start with the standard AWS basics, access key, and secret keys, then eventually add in SSO and other things relevant to end users.