feat!: Make DropdownAPI consistent and fix keyboard handling

[jquense]

Also removes the need for a wrapping element

[taion]

question: do these get properly enqueued/deduped, or could we end up with a double-rerender?

[jquense]

I'm fairly sure it does, maybe not a big deal either way idk

[jquense]

I realized recently that we don't handle escape inside of a modal for dropdowns which leads to both firing. Bootstrap calls preventDefault and stopPropagation for those, but that's tricky here given that this now fires after react sees the event.

Should try and attach the events in react via props? I was trying to avoid extra event merging needed by users, but maybe that's ok here? Alternatively i could do the capture phase tagging etc

[taion]

ohh that's unfortunate.

these don't even both go through root close wrapper, right?

i guess we could have some shared WeakMap or something there to ensure events are only processed once? would also address #836