feat(docs): proposal loading mechanism

[ArtieReus]

Summary

The goal of this proposal is to consolidate all information regarding the extension loading mechanism into a single, comprehensive document. It aims to clearly outline all discussed options with when possible with a decision, eliminating any potential misunderstandings, and to establish consensus on the approach that best fits the project’s needs.

Changes Made

• Reviewed documentation in Epics, Emails and PFDs
• Added new concept of Kubernets as CDN

Related Issues

• [EPIC](greenhouse): Architecture and Modularization #275

[changeset-bot]

⚠️ No Changeset found

Latest commit: ee42d3f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[andypf]

👍

[taymoor89]

Thanks @ArtieReus for preparing this document. 👍

Despite having concerns, IMO we might not need to take this architectural decision right now because whether we do it in one way or the other it barely affects the overall functionality of the host or extension applications. And this loading mechanism can be changed later in a less intrusive manner when we'll have more more information/requirements.

[hodanoori]

This helped me to be informed about the new generation of our shell app, so thank you 👍

[hodanoori]

lgtm

[guoda-puidokaite]

Thank You for the call! I'm informed. 🙏🙈🤪