POC - auro-popover: Native support

[braven112]

Is your feature request related to a problem? Please describe.

We would like to incorporate the new native HTML version of popover. We need to first identify the scope of this work. What components will end up changes as a result of this.

We have had a number of issues where the popover doesn't appear where it should and our hypothesis is that leveraging the native popover will be more reliable and allow us to get rid of popover.js

Describe the solution you'd like

This component is either retired and replaced with native support or this component is updated to utilize native html support.

Describe alternatives you've considered

No response

Additional context

This component is often used in auro-dialog for form components and it is in those state where we see the majority of issues.

Exit criteria

1. a POC version of Auro-Popover has been created that uses native Popover to validate that it will fit our needs
2. Nees to show using a popover in full screen desktop, mobile, and in a bib.
3. The POC is not complete until we also outline what the keyboard accessibility experience is out of the box.
4. Anything that native popover doesn't do, but popperJS does do (that we use) is documented and brought to the team for discussion about how we want to approach that issue.
5. Determine how Native popover will impact the mobile experience and if it will be suitable for mobile

[jordanjones243]

The outcome of this POC was that it is not what we want to use to replace PopperJS because of the lack of positioning API needed to achieve how we want the component to behave. I am not closing this out yet, but moving back to investigating, as there was some discussion about using the modal dialog features provided in Native Popover in order to achieve the new dropdown mobile look.

[Patrick-Daly-AA]

Native Popover will not meet our needs. We are investigating Floating UI instead.

[jason-capsule42]

Duplicate of #218