Improved handling of invalid mobile numbers

[hggutvik]

Description

When placing notification orders where SMS is involved, mobile numbers that include invalid characters (like letters) now produces response code 400 instead of 500. Additionally, the general response for such invalid numbers is changed:

• Before: "Invalid mobile number format".
• Now: "Mobile number can contain only '+' and numeric characters, and it must adhere to the E.164 standard."

Affected endpoints:

• POST /notifications/api/v1/orders/sms
• POST /notifications/api/v1/orders

The MobileNumberHelper class, used by Validators to perform number validation, now has a try/catch for when PhoneNumberUtil throws NumberParseException. These exceptions now result in the method IsValidMobileNumber returning false.

Related Issue(s)

• Invalid characters allowed in mobileNumber Field of /notifications/api/v1/orders Endpoint #619

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)
• All tests run green

Documentation

• User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

[SandGrainOne]

Please just add a test for a Norwegian name in the email address.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud