chore(compass-web): add an interface to propagate the tab closing checks for before unload interception COMPASS-8033

[gribnoysup]

Part of the change that should allow us to warn users when navigating away from the data explorer route when some tabs are in "dirty" state. We can't encapsulate all this logic inside Compass because we will have to interface with react-router on the mms side for this to work, so instead of this, we'll allow mms to get a reference to the callback that the code there will be able to run to do the check. Property name is a bit weird, but I couldn't come up with something better, suggestions are welcome

[nbbeeken]

What is an example of something that makes a tab dirty?

[Anemy]

@nbbeeken An example of a tab in the "dirty" state would be if a user has an written a query/aggregation in the tab and hasn't saved.
You can look up onTabClose and onTabReplace in the code base to see them currently.

[Anemy]

Should we add something to the sandbox env that uses this? We can add the window.onbeforeunload to

compass/packages/compass-web/sandbox/index.tsx

Line 98 in be5501a

<CompassWeb

Fine as is, it may be a nice test to add or something for the npm run start-web environment to use.

[gribnoysup]

@Anemy good point, I'll keep it to a separate PR to make sure it's not affecting / accounted for in the e2e tests