Export `ClientEnv` type constructor for external use

[nattybear]

Currently, the module does not export the type constructor ClientEnv, which makes it impossible to use it directly in user code.

For example, ClientEnv is often reused across multiple parts of an application. In such cases, one might want to construct it once and retrieve it later inside a ReaderT using ask. However, this pattern requires access to the type constructor ClientEnv, which is currently not exported.

I’m considering opening a PR that exports only the type constructor ClientEnv (while keeping other exports unchanged). Before doing so, I’d like to hear the community’s thoughts:

Would exporting the type constructor cause any unwanted side effects?

Have others encountered the same limitation?

Any feedback or prior discussion on this would be appreciated.