chore: add infrastructure for standalone

[liamdebeasi]

Issue number: N/A

---

What is the current behavior?

We do not have a way of separating lazy loaded components from standalone components. This is important because developers who wish to use Ionic UI components as standalone components do not want their component implementation to use the lazy loaded component.

What is the new behavior?

This PR creates two submodules within @ionic/angular:

@ionic/angular/common located at packages/angular/common:

• This is where logic that is shared between lazy loaded and standalone components live. For example, if you want to have a lazy loaded IonPopover and standalone IonPopover, you could put the base component implementation here and then have the lazy loaded/standalone implementations extend from this base implementation.

@ionic/angular/standalone located at packages/angular/standalone:

• This is where the standalone component implementations live. It was added as a separate entry point to avoid any lazy loaded logic from accidentally being pulled in to the final build.

Does this introduce a breaking change?

• Yes
• No

Other information

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.