Translate locally Creative Commons answers not translated by CC API

[toniprieto]

References

• Fixes Labels for Radio buttons in Creative Commons License Selection Appear in English when French language selected DSpace#9393
• 8.x port: [Port dspace-8_x] Translate locally Creative Commons answers not translated by CC API #5032

Description

This PR introduces local translations for Creative Commons license answer labels that are returned untranslated by the CC API.

Note: This is a temporary workaround while the legacy CC API integration is still in use. See: DSpace/DSpace#9397

Instructions for Reviewers

List of changes in this PR:

• Updated the CC License submission component to translate Creative Commons answer labels locally instead of displaying raw values from the CC API.
• Added new i18n translation keys for CC license answers (Yes, No, ShareAlike) in English, Spanish, and Catalan

To test it:

• Enable the cclicense step in item-submission.xml.
• Comment out or leave empty the cc.license.locale property in dspace.cfg.
• Configure supported locales in dspace.cfg, for example:

webui.supported.locales` = en, ca, es

• Start a new item submission and verify that CC license answers are properly translated according to the selected UI language.

Checklist

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using npm run lint
• My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
• My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• My PR aligns with Accessibility guidelines if it makes changes to the user interface.
• My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
• My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
• If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.