Reintroduce client autoloads

[nickfloyd]

RE: #1351 | #1425 | #1422 for more information

The original change for this PR was introduced in v4.23.0.

For the most part, this change is/was beneficial but after @collinsauve highlighted an issue that he was having as a result of this change we realized other areas where autoloading could cause issues due to modules not being loaded or load order even - details here.

• We need to rollback the original PR and post another release (Reverts autoloading of modules change #1428)
• Make a note in the original changelog of this issue
• We need to consider optional ways to introduce this change (as part of the instantiation opts, etc...)
• Reintroduce this change as an opt-in feature

[collinsauve]

Thanks for that investigation @nickfloyd - makes sense now why we were having this issue.

My 2 cents, though I'm just one of many users: We can probably work-around the breaking change, now that we know the cause. Calling it out in a changelog somewhere (with a documented workaround 🙏) would be helpful for others.

[nickfloyd]

@collinsauve fantastic idea, once I get the "rollback" done I'll annotate the release notes. Thanks, and great catch!

[nickfloyd]

Thanks for that investigation @nickfloyd - makes sense now why we were having this issue.

@timrogers was the one that finally tracked it down I believe (here). I'll reach out to him to get his thoughts on what he feels would be a good workaround to document for others might be.

[github-actions]

👋 Hey Friends, this issue has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Please add the Status: Pinned label if you feel that this issue needs to remain open/active. Thank you for your contributions and help in keeping things tidy!