Modal to prevent losing REST datasource changes

[adrinr]

Description

REST datasources currently behave quite differently from the other datasources and the rest of the platform, as it is one of the few points where we don't autosave on actions: the user is required to save via the save click. This might be confusing as the UI and some of its elements might give the impression that the data is persisted on change. This will be even more problematic as we are changing some of its configuration elements from dropdowns to context buttons and menus.
This PR introduces a mechanism to detect if you are leaving a REST config with unsaved changes. If this is the case, the user will have 2 options:

1. Leave discarding the changes
2. Leave saving the changes
3. Close the modal and stay on the current page (this required some extra props on the confirm modal)

Screenshots

No modal when no changes

Modal appears when there are changes

Saving on exiting the screen

Discard changes on exit

Closing the modal will prevent from exiting

On new endpoint, we will validate if it's saved

We will not validate new endpoint "save" status if there is no changes at all

Launchcontrol

Confirm modal when leaving a rest configuration page with unsaved changes

[linear]

BUDI-9127 Create oAuth2 section

[qa-wolf]

QA Wolf here! As you write new code it's important that your test coverage is keeping up.
Click here to request test coverage for this PR!

[aptkingston]

LGTM! The confirm util is very nice.

NAB - could we update the "Save and continue" button to be a CTA variant instead? The current red button makes it look like saving is a bad/dangerous thing, but it's probably what they want to press.

[aptkingston]

This is a nice util to have 👌

[adrinr]

LGTM! The confirm util is very nice.

NAB - could we update the "Save and continue" button to be a CTA variant instead? The current red button makes it look like saving is a bad/dangerous thing, but it's probably what they want to press.

Good catch! Updated: