fix: Additional input validation for category setting

[KirylHatalski]

Ticket: AUT-1480

Steps to reproduce:

• Open an existing test in the Authoring mode
• In the "Categories" field add a new category that contains special characters (e.g. PrøvÆØÅ) or dot (e.g. category.1)
• In "Scoring" section select "Total score" for "Outcome processing"
• Check the "Category score" checkbox
• Click "Save"
• Export the test and check the test.xml for "outcomeProcessing"

What is changed:
Now in section Categories property is not possible to set incorrect values.

[github-actions]

Version

Target Version	48.12.2
Last version	48.12.1

There are 0 BREAKING CHANGE, 0 feature, 1 fix

[github-actions]

Front-end summary Node 18

💯 Total	✅ Passed	⏭️ Skipped	❌ Failed
709	709	0	0

[Karol-Stelmaczonek]

• New code is covered by tests (if applicable)
• Tests are running successfully (old and new ones) on my local machine (if applicable)
• New code is respecting code style rules
• New code is respecting best practices
• New code is not subject to concurrency issues (if applicable)
• Feature is working correctly on my local machine (if applicable)
• Acceptance criteria are respected
• Pull request title and description are meaningful

[tikhanovichA]

LGTM

• New code is covered by tests (if applicable)
• Tests are running successfully (old and new ones) on my local machine (if applicable)
• New code respects code style rules
• New code respects best practices
• Feature is working correctly on my local machine (if applicable)
• Acceptance criteria are respected
• Pull request title and description are meaningful
• Pull request's target is not master
• Commits are following conventional commits
• Commits messages are meaningful
• Commits are atomic

[viktar-dzmitryieu-tao]

• New code is covered by tests (if applicable)
• Tests are running successfully (old and new ones) on my local machine (if applicable)
• New code is respecting code style rules
• New code is respecting best practices
• New code is not subject to concurrency issues (if applicable)
• Feature is working correctly on my local machine (if applicable)
• Acceptance criteria are respected
• Pull request title and description are meaningful
• Pull request's target is not master

[jsconan]

Code review only.

One comment though: do not mix code bundles with other code changes in the same commit. This is not atomic, and this will make backports trickier

Review Checklist

• New code is covered by tests (if applicable)
• Tests are running successfully (old and new ones) on my local machine (if applicable)
• New code respects code style rules
• New code respects best practices
• New code is not subject to concurrency issues (if applicable)
• Feature is working correctly on my local machine (if applicable)
• Acceptance criteria are respected
• Pull request title and description are meaningful
• Pull request's target is not master
• Commits are following conventional commits
• Commits messages are meaningful
• Commits are atomic