feat(validation): update Company validation expression

[typecastcloud]

Description

The Company validation expression in the ValidationExpressions class has been updated to support a wider range of characters, including special characters and non-Latin alphabets.

Why

This change ensures that the validation accurately captures company names from different languages and regions.

Issue

Fixes: eclipse-tractusx/portal#360
Refs: eclipse-tractusx/portal-frontend-registration#250

Checklist

• I have followed the contributing guidelines
• I have performed a self-review of my own code
• I have successfully tested my changes locally
• I have added tests that prove my changes work
• I have checked that new and existing tests pass locally with my changes
• I have commented my code, particularly in hard-to-understand areas

[Phil91]

@typecastcloud please execute ./scripts/update_framework_versions.sh minor on root of the project to update the Nuget Packages

[ntruchsess]

@MaximilianHauer technically the suggested rexexp looks fine. I verified it does what the comment in the code describes. Please confirm this may be merged (the associated ticket is already in progress with milestone assigned)

[MaximilianHauer]

@ntruchsess fine for me as we need to provide more international support and BPDM aligned with us that every request will be independently checked on their side and we would not provide any benefit with our restrictions to them.
@typecastcloud please be aware that we currently filter special characters in the wallet api during the wallet creation. if the company name would consist only out of special characters it could cause issues.
@Phil91 and me look into this one already.

[ntruchsess]

@typecastcloud please rebase on main and resolve the conflict in CHANGELOG.md (please consider to allow commiters to push to your repository or at least the open PR branches - if conflict-resolution is straightforward it's likely we cleanup such conflicts 'on-the-fly' while doing the review)

[typecastcloud]

@typecastcloud please rebase on main and resolve the conflict in CHANGELOG.md (please consider to allow commiters to push to your repository or at least the open PR branches - if conflict-resolution is straightforward it's likely we cleanup such conflicts 'on-the-fly' while doing the review)

Hi @ntruchsess, I always had this on as default and I don't know why this was not possible with this PR. Sorry! I was sick for the last few days.

Rebased and comments are updated.

[sonarcloud]

Quality Gate passed

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 SonarCloud