fix(overlays): presenting an overlay does not create nested elements

[sean-perkins]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
  • Some docs updates need to be made in the ionic-docs repo, in a separate PR. See the contributing guide for details.
• Build (npm run build) was run locally and any changes were pushed
• Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

When overlays are presented without a user defined component, the overlay will continue to create elements at the root of the overlay and append the contents of the teleported component inside of it. This results in scenarios where in implementations like ion-datetime-button with an ion-modal, the ion-modal will create a nested DOM tree of .ion-page elements.

Issue URL: #26117

What is the new behavior?

• Inline overlays do not create nested root nodes from the delegate
• DatetimeButton with a modal does not create nested .ion-page elements

Does this introduce a breaking change?

• Yes
• No

Other information

Dev-build: 6.3.3-dev.11666207854.1e96b6a8

This is the same fix that we landed on for this feature: #26153, but since that is targeted for v7, it would be great to resolve this specific bug for v6.

[sean-perkins]

Should we be reflecting the presentation instead of evaluating the property value, like we are doing in this flaky test: https://github.com/ionic-team/ionic-framework/blob/main/core/src/components/datetime-button/test/basic/datetime-button.e2e.ts#L23-L29?

[liamdebeasi]

Great job!