i18n: Improve handling of file existence check in compileCatalog

[Samk13]

❤️ Thank you for your contribution!

Description

• Add a check for the existence of the file before attempting to read it
• Log an error message if the file does not exist
• Improve readability by extracting the file existence check into a function

Fix this error where it will stop execution if one of the languages mises .po file:

npm run compile_catalog

> compile_catalog
> node ./scripts/compileCatalog.js

node:fs:573
  return binding.open(
                 ^

Error: ENOENT: no such file or directory, open './messages/en/messages.po'
    at Object.openSync (node:fs:573:18)
    at readFileSync (node:fs:452:35)
    at Object.<anonymous> (/home/user/INVENIO/issues/invenio-rdm-records/invenio_rdm_records/assets/semantic-ui/translations/invenio_rdm_records/scripts/compileCatalog.js:36:7)
    at Module._compile (node:internal/modules/cjs/loader:1358:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
    at Module.load (node:internal/modules/cjs/loader:1208:32)
    at Module._load (node:internal/modules/cjs/loader:1024:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12)
    at node:internal/main/run_main_module:28:49 {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: './messages/en/messages.po'
}

Node.js v20.13.1

After:

npm run compile_catalog

> compile_catalog
> node ./scripts/compileCatalog.js

File not found: ./messages/en/messages.po for language en

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.

Frontend

• I've followed the CSS/JS and React guidelines.
• I've followed the web accessibility guidelines.
• I've followed the user interface guidelines.

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.