6349 fix double confirm

[lache-melvin]

Fixes #6349

👩🏻‍💻 What does this PR do?

JSON forms has an isDirty check on navigation baked in. So we don't need the extra custom one :)

💌 Any notes for the reviewer?

🧪 Testing

• Edit a patient (or create one)
• Click cancel instead of save
• You only get one confirmation modal before you are navigated away

📃 Documentation

• Part of an epic: documentation will be completed for the feature as a whole
• No documentation required: no user facing changes or a bug fix which isn't a change in behaviour
• These areas should be updated or checked:
  1.
  2.

📃 Reviewer Checklist

The PR Reviewer(s) should fill out this section before approving the PR

Breaking Changes

• No Breaking Changes in the Graphql API
• Technically some Breaking Changes but not expected to impact any integrations

Issue Review

• All requirements in original issue have been covered
• A follow up issue(s) have been created to cover additional requirements

Tests Pass

• Postgres
• SQLite
• Frontend

[lache-melvin]

fixed this in the edit schema last week but forgot the create schema 😁

[github-actions]

Bundle size difference

Comparing this PR to main

Old size	New size	Diff
5.97 MB	5.97 MB	-186 B (-0.00%)

[aimee-mcneil-melville]

Works like a beaut!
I did notice that when editing a patient, if a field is edited and not blurred before clicking one of the other tabs, the information won't save/confirm for saving.

This is not related to your issue or fix though, so I'll raise it separately!

[aimee-mcneil-melville]

Actually - this looks like it's only if it's an immediate change of tab - after half a second it prompts the save!