GN-4359: improve publish page translations

[elpoelma]

Overview

This PR improves and fixes some of the translations on the different meeting publication pages.

connected issues and PRs:

Jira ticket

How to test/reproduce

Visit the publication pages and try to find any missing/wrong translations.

Checks PR readiness

• UI: works on smaller screen sizes
• npm lint

[x-m-el]

Non-PR notes:

• There are still some missing translations outside of publishing pages. I see this PR is specifically for that, but don't see a ticket for the other pages.
  So I'll limit this review the publish pages and make a jira ticket for those

• any reason 'no-bare-strings': true, in .template-lintrc.js does not make the linting fail for all the bare strings?

Review:

Text from outside sources aren't translated. It is in Dutch (probably the main used language), so I'm not sure if this is a "real" problem. I'm guessing you can still translate these somehow, but as far as I can see not with ember-intl, so probably not trivial.

• all other (normal) translations seem to be in order. Also no typos in translations nor new bugs.

[elpoelma]

Non-PR notes:

* There are still some missing translations outside of publishing pages. I see this PR is specifically for that, but don't see a ticket for the other pages.
  So I'll limit this review the publish pages and make [a jira ticket](https://binnenland.atlassian.net/browse/GN-4390) for those

* any reason `'no-bare-strings': true,` in `.template-lintrc.js` does not make the linting fail for all the bare strings?

Review: Text from outside sources aren't translated. It is in Dutch (probably the main used language), so I'm not sure if this is a "real" problem. I'm guessing you can still translate these somehow, but as far as I can see not with ember-intl, so probably not trivial.

* all other (normal) translations seem to be in order. Also no typos in translations nor new bugs.

• On the 'no-bare-strings' rule, it only fails when the template contains untranslated strings that are directly displayed, not on untranslated strings that are passed as an argument to another component for example.

• On the text coming from the outside sources, I think we need to find a way to add some sort of internationalization on our backend services. We could probably implement it using something like this: https://www.npmjs.com/package/i18n

[x-m-el]

for backend translations issue created:
https://binnenland.atlassian.net/browse/GN-4396