Add additional OA fee in OPF components

[autavares-dev]

References

Related back-end PR: DSpace/DSpace#12629

Description

Adds information about additional OA fee in the OPF components.

When a version in the OPF response contains an additional OA fee, renders an icon and text showing it.

Example

In OPF:

In the forms:

Instructions for Reviewers

With the related back-end PR running, start a new submission and enter some ISSN containing an additional OA fee.

It should now be displayed in the OPF section in the form.

List of changes in this PR:

• Adds property additionalOpenAccessFee in the OPF response
• Conditionally renders icon + text in a version that contains additional OA fee
• Adds new i18n tag submission.sections.jisc.publisher.policy.additional-oa-fee
  • Translations added in en.json5, pt-BR.json5 and pt-PT.json5
  • For languages without translations to other JISC related tags, the new tag was added with the comment // TODO New key - Add a translation and english text
  • For languages with translations to other JISC related tags, the new tag was added with the comment // TODO Source message changed - Revise the translation and translated text using Google Translate.

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.
• If my PR fixes an issue ticket, I've linked them together.