js-tests: add translation build to tests

[tmorrell]

❤️ Thank you for your contribution!

Description

We should include the js translation build steps in the CI, to avoid issues like https://github.com/inveniosoftware/invenio-app-rdm/actions/runs/16355943075/job/46214227478 that only show up when running the release.

Checklist

Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

• I'm aware of the code of conduct.
• I've created logical separate commits and followed the commit message format.
• I've added relevant test cases.
• I've added relevant documentation.
• I've marked translation strings.
• I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
• I've NOT included third-party code (copy/pasted source code or new dependencies).
  • If you have added third-party code (copy/pasted or new dependencies), please reach out to an architect on Discord.

Reminder

By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

1. You license your contribution under the same terms as the current repository’s license.
2. You agree that you have the right to license your contribution under the current repository’s license.

[utnapischtim]

should be combined with #12 and the ongoing effort to make the translation easier

[tmorrell]

I think we should merge this one now. Otherwise the package-lock issue may crop up when we try to do a release. We can then upgrade or change both the release and test workflows when we have a better translation routine.

[Samk13]

Question: Do we actually need inputs.translations-working-directory here?
We never use it translation_dir is auto-detected via determine_js_path (same pattern as the publish workflow).

Can we align tests-js.yml with the publish workflow? i.e., drop inputs.js-working-directory and inputs.translations-working-directory, rely on determine_js_path (steps.determine_js_path.outputs.translation_dir) for gating + working-directory, and copy the same Node setup + build steps. This removes unused inputs and matches the behavior we ship in publish.

[ntarocco]

@zzacharo since you have followed the translations developments, can you please have a look?