[MDS-6634] Conflict between "Add Report Requirement" form and condition form

[taraepp]

Objective

• currently, adding a report requirement to a condition with unsaved changes will revert those changes
  • not just because the form closes, but also because of the refreshing data function (which is a whole can of worms)
• as a solution, added a popconfirm when the condition form is dirty and the user clicks to add a report
• also, because users lose their place, not closing out the condition form after changes are saved
  • this is kind of an experiment to see if they like it better this way. Pretty easy to revert.
  • makes it easy for adding a report later,
  • and then they can just click another condition to edit it if they like (they don't have to click the X button to close editing if they're truly done)

MDS-6634

Why are you making this change? Provide a short explanation and/or screenshots

[sonarqubecloud]

Quality Gate passed for 'bcgov-sonarcloud_mds_minespace-web'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed for 'bcgov-sonarcloud_mds_common'

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed for 'bcgov-sonarcloud_mds_core-web'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud