feat: LEAP-1198: Add labeling unsaved changes warning

[Gondragos]

This introduces a functionality of blocking any navigation while there are some unsaved changes in the labeling config.

It provides:

• a new component LeaveBlocker that manages blocking of all cases of navigation
• a new component UnsavedChanges that uses LeaveBlocker and provides a modal unsavedChangesModal for action confirmation dialog
• browserHistory improvement to handle history blocks from LeaveBlocker and indicate right that it is blocking
• fix for handeling popstate at AsyncPage.js for preventing false positive triggering while history is blocked
• add unsaved changes indication
• make saveConfig work with ProjectProvider to avoid caching problems
• add useful field into ApiProvider including it's types
• allow updateProject to return errors to handle them in editor
• fix project caching on calling updateProject

PR fulfills these requirements

• Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
• Tests for the changes have been added/updated (for bug fixes/features)
• Docs have been added/updated (for bug fixes/features)
• Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
• Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)

• Product design
• Backend (Database)
• Backend (API)
• Frontend

Does this change affect security?

I do not think so.

What feature flags were used to cover this change?

fflag_feat_front_leap_1198_unsaved_changes_180724

Does this PR introduce a breaking change?

(check only one)

• Yes, and covered entirely by feature flag(s)
• Yes, and covered partially by feature flag(s)
• No
• Not sure (briefly explain the situation below)

I've tried to avoid breaking changes. But we will see...

What level of testing was included in the change?

(check all that apply)

• e2e
• integration
• unit

Which logical domain(s) does this change affect?

Labeling Config, ApiProvider, ProjectProvider, BrowserHistory

[netlify]

✅ Deploy Preview for label-studio-docs-new-theme canceled.

Name	Link
🔨 Latest commit	abd203f
🔍 Latest deploy log	https://app.netlify.com/sites/label-studio-docs-new-theme/deploys/66aafbe7ede5180008f52498

[netlify]

✅ Deploy Preview for heartex-docs canceled.

Name	Link
🔨 Latest commit	abd203f
🔍 Latest deploy log	https://app.netlify.com/sites/heartex-docs/deploys/66aafbe7ee782800081cc849

[yyassi-heartex]

looks good overall - my only request would be to add unit tests for the new component

[Gondragos]

/git merge develop

Workflow run
Successfully merged: 17 files changed, 28 insertions(+), 632 deletions(-)