feat: Explore popovers should close on escape

[diegomedina248]

SUMMARY

This PR enables the popovers in the explore to be closed when hitting the escape key.
Also, improves the locking of the explore scroll, so that the popovers are pinned to the triggering div until they're closed.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

No way to visually show the difference, so this is the actual result:

new.mov

TESTING INSTRUCTIONS

In the explore:

• Try to edit the Data, be it metrics, columns, dimensions, filters, etc, and ensure it continues to work as before
• Hit the escape key while a popover is open and ensure it closes
• Ensure you can still interact with the popver (type, click, etc).

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[codecov]

Codecov Report

Merging #19902 (2fd9355) into master (fdf48c6) will increase coverage by 0.00%.
The diff coverage is 95.45%.

@@           Coverage Diff           @@
##           master   #19902   +/-   ##
=======================================
  Coverage   66.54%   66.54%           
=======================================
  Files        1714     1714           
  Lines       65102    65118   +16     
  Branches     6725     6729    +4     
=======================================
+ Hits        43321    43335   +14     
- Misses      20069    20070    +1     
- Partials     1712     1713    +1     

Flag	Coverage Δ
javascript	51.27% <95.45%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...ponents/controls/ControlPopover/ControlPopover.tsx	89.09% <95.45%> (-0.66%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fdf48c6...2fd9355. Read the comment docs.

[codemaster08240328]

Totally, I don't think that introducing visible state here is a good idea.
We can control visibleProps.
Currently you are mixing visible state and visible props to control visible, but it is not a good idea.

[diegomedina248]

We need the visible state locally to control the popover in this component.
The "visible" prop can be undefined, (leaving the component in an uncontrolled manner), that's why we need to take over the control, and can't rely on simple calling the onVisibleChange callback

[rusackas]

LGTM

[sadpandajoe]

🏷️ preset:2022.19