Feature/AUT-3414/Align categories that activate the TextToSpeech tool

[jsconan]

Related to: https://oat-sa.atlassian.net/browse/AUT-3414

Requires:

• https://github.com/oat-sa/extension-tao-texthelp/pull/70

Summary

Add support for multiple categories to activate presets in the test authoring.
The concepts is as follows:

• a preset can be activated using any of the declared categories (support for legacy categories)
• when saving the test, only the main declared category of the preset is persisted

The main example for this is the text-to-speech tool which used to be activated using the category x-tao-option-textToSpeech. However, TAO Advance expects it to be x-tao-option-tts. Both categories will be supported, but only the later will be kept when updating a test.

How to test

Prerequisite: have the extension taoTextHelp installed with the branch feature/AUT-3414/align-tts-category

• create/open a test in Authoring
• activate the test taker tool TextToSpeech
• save the changes
• export the test, then open the archive an check that the category x-tao-option-textToSpeech is set appropriately
• check out the branch on both taoQtiTest and taoTextHelp: git checkout -t origin/feature/AUT-3414/align-tts-category
• update TAO
• open the same test in Authoring
• check that the taker tool TextToSpeech is still activated
• deactivate the tool, then activate it again
• save the changes
• export the test, then open the archive an check that the category x-tao-option-tts is set appropriately

[github-actions]

Front-end summary Node 18

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

[github-actions]

Version

Target Version	48.4.0
Last version	48.3.7

There are 0 BREAKING CHANGE, 2 features, 0 fix

[gabrielfs7]

Thanks for improving the code, @jsconan

I did a check on PHP code level only and looks good. We can have a demo to check functionality if possible.

• New code is covered by tests (if applicable) JS code is
• 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

[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

[shaveko]

Looks good!