fix: unblock acp via databricks

[alexhancock]

When goose runs via goose acp we don't have a multi-threaded runtime available

goose/crates/goose-cli/src/commands/acp.rs

Line 680 in 5b93ee5

let local_set = tokio::task::LocalSet::new();

Therefor, this bombs when goose is running via acp and with databricks

tokio::task::block_in_place(|| {
  tokio::runtime::Handle::current().block_on(async { ... })
}

Removing it doesn't seem to break anything I can find via normal usage, and unblocks using goose via acp and with databricks

[Copilot]

Pull Request Overview

This PR simplifies async code by removing unnecessary nested async runtime handling. The from_env function was using tokio::task::block_in_place with nested async blocks to call fetch_supported_models().await, which is redundant since from_env itself is already an async function.

• Removed nested tokio::task::block_in_place and block_on wrapper
• Simplified direct async/await call to fetch_supported_models()
• Maintained identical conditional logic for model configuration

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.