dagster_azure: be able to import without fake impls

[futurwasfree]

What's the issue?

Currently when I import the following symbols in my production setup:

from dagster_azure.adls2.io_manager import adls2_pickle_io_manager
from dagster_azure.adls2.resources import adls2_resource

I'm also getting all the fake_adls2_resources imported, as it's described in adls2/__init__.py:

from dagster_azure.adls2.fake_adls2_resource import (
    FakeADLS2Resource as FakeADLS2Resource,
    FakeADLS2ServiceClient as FakeADLS2ServiceClient,
    fake_adls2_resource as fake_adls2_resource,

This easily adds 0.3-0.5 seconds to overall import/startup time.

Wondering if it's possible to exclude fakes from init.py or switch to Python namespace subpackages inside (with no init.py on this level)?

What did you expect to happen?

I expect only real/production implementations to be imported when executing these two import lines.

How to reproduce?

No response

Dagster version

dagster, version 1.9.4

Deployment type

Dagster Helm chart

Deployment details

No response

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

[ion-elgreco]

@futurwasfree you can make a pr for it, probably will be accepted

[futurwasfree]

@ion-elgreco and I've just did here: #26754. thanks for looking into it!