Replace `nest_asyncio` if possible in `AlchemiscaleClient`

[dotsdl]

nest_asyncio appears to no longer be developed, and though it appears to work fine for now, it may be worth pursuing alternatives. We only use it in a couple AlchemiscaleClient methods that make use of asyncio, allowing them to be used in e.g. Jupyter notebooks without issues.

[passionworkeer]

Great issue! A few alternatives to consider:

1. Check if already in event loop: Use asyncio.get_running_loop() with try/except to detect notebook environments
2. Thread-local storage: Store the loop in a thread-local variable instead of patching
3. Client-side only: Move the asyncio logic to a thin wrapper that users import explicitly in notebooks

For approach #1:
def get_client(...):
try:
loop = asyncio.get_running_loop()
# Already in async context
except RuntimeError:
# Not in async context, create new event loop
...

This avoids the global patch. Hope this gives you some direction!

[passionworkeer]

A few alternatives to consider:

1. Remove nested event loop usage - Refactor the client methods to accept an existing event loop instead of creating one
2. Use �syncio.run() - For Jupyter, you can use �syncio.run() in each cell instead of patching the event loop
3. Lazy initialization - Check �syncio.get_running_loop() and only call
   est_asyncio.apply() when needed

The cleanest fix is usually option 1: make the async methods accept an optional loop parameter so callers can pass their own.