Add Bedrock Cloud Model provider

[5herlocked]

Closes #16544

Release Notes:

• Added support for Bedrock as an FM provider
• Added rudimentary support for AWS credential management to Zed

[5herlocked]

This still needs to be updated to the new method of managing models, going to spend the next couple of weeks migrating to it.

[5herlocked]

Zed maintainers, would appreciate some guidance on how the ZedPro things are setup and if it makes sense to pass the Bedrock models into it.

On a cursory reading of the feature, i don't believe it does -- however, i am open to working with the bedrock service team to make it a reality.

[rgbkrk]

I don't think you need to pass through the bedrock models through the collab service, as Zed would need to run their own bedrock setup. I'd just do the API key / AWS credentials route.

[SomeoneToIgnore]

Unfortunately, our CLA bot is broken, so I have to substitute for it for a while:

We require contributors to sign our Contributor License Agreement, and we don't have @5herlocked on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

[5herlocked]

Will get it done post a legal review of the docs (just want to make sure AWS doesn't have an issue with it)

[5herlocked]

@cla-bot check

[5herlocked]

Some conversations with the AWS SDK team later, the best recommendation from them is to SigV4 the requests manually and then just interact with the raw API, will pivot to that in the coming weeks.

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have @deepsource-io[bot] on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

[5herlocked]

@cla-bot check

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have @deepsource-io[bot] on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have @deepsource-io[bot] on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have @deepsource-io[bot] on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

[5herlocked]

@SomeoneToIgnore Please call off the cla-bot 😂

[SomeoneToIgnore]

I'm afraid I was only able to act like one when it was down.
I suspect you need to alter f798bf4 commit's author or ask that bot to sign the CLA 🙂

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have @deepsource-io[bot] on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

[5herlocked]

The tests are failing with some GlobalTokio unwrap that is outside my codebase, can someone look at the full breakdown and understand what's going on? Or i can setup a graceful failure in Bedrock in case of a failed tokio spawn.

[5herlocked]

If we can get all tests to pass, i would be fine taking on tool use as a followup action item rather than blocking this PR

[5herlocked]

Yeah @mikayla-maki might need your insight on this, looks like GPUI tokio is failing to get a tokio handle on restart? which is causing the bedrock provider to crash in the tests.