Fix block_on usage in connect

[avinassh]

fixes #2032

[Copilot]

Pull Request Overview

This PR addresses issue #2032 by fixing the usage of tokio’s block_on functionality in the database bootstrap process. Key changes include:

• Replacing the previous tokio::task::block_in_place call with a conditional branch based on the presence of a synchronization context.
• Introducing a new branch to handle runtime availability via tokio::runtime::Handle::try_current(), with distinct handling for when a current runtime exists and when it does not.

Comments suppressed due to low confidence (1)

libsql/src/database.rs:695

• Consider handling potential errors when building the Tokio runtime instead of using unwrap(), to avoid an unexpected panic in production environments.

.build().unwrap();

[avinassh]

Okay, this might not be the proper way to handle this.

https://greptime.com/blogs/2023-03-09-bridging-async-and-sync-rust

https://stackoverflow.com/a/66280983