Verify - Amalgamation Out Filing – API Error Not Handled in UI

**Describe the bug in current situation**
When submitting an Amalgamation Out filing, if the entered jurisdiction information does not match the active Consent to Amalgamate Out, the UI does not handle the API validation error gracefully. Instead, the raw backend error is displayed to the user.

**Steps to Reproduce**
Steps to reproduce the behaviour:
1. Complete the Consent to Amalgamate Out process.
2. Log in as a Staff user.
3. Create an Amalgamation Out filing.
4 Enter jurisdiction information that does not match the existing Consent to Amalgamate Out.
Submit the filing.

**Actual/ observed behavior/ results**

{"errorMessage": "API backend third party service error.", "rootCause": {
**"errors": [
{
"error": "No active consent amalgamation out for this date and/or jurisdiction.",
"path": "/filing/amalgamationOut/amalgamationOutDate"
}**
],
"filing": {
"amalgamationOut": {
"amalgamationOutDate": "2026-07-02",
"details": "Amalgamation Out\nTEsting",
"foreignJurisdiction": {
"country": "CA",
"region": "NS"
},
"legalName": "3000098 B.C. LTD."
},
"business": {
"foundingDate": "2026-07-23T15:32:40.000+00:00",
"identifier": "BC3000098",
"legalName": "3000098 B.C. LTD.",
"legalType": "BC"
},
"header": {
"authorizationReceived": true,
"date": "2026-07-23",
"email": "vvr@gmail.com",
"name": "amalgamationOut",
"waiveFees": true
}
}
}
}

**Expected behavior**
Proper error message like Continuation Out