* use variables in the translation strings rather than string
  concatenation
* use double quotes for strings for consistency and less escaping

Tsepelakis, Sotirios authored 1 week ago and Moser, Maximilian committed 3 days ago

* Includes sub-pages 'API Docs', 'About DAMAP' & 'About VRE'

* because most of the time we want to manage the new accounts, which of
  course have the highest IDs

* also add `.npmrc` which will likely be needed for PNPM support
* this is the extent for our PNPM support right now, as further changes
  in `invenio-cli` are required
* this is based on work from Alex (CERN) and Christoph (TU Graz)

* because we're enabling the community-submission request workflow again

* 10 was a bit much...

* add the uploader's secondary email in CC if provided by the user
* remove the option to add the inquirer's specified email address to CC,
  to avoid leaking the email addresses of the uploader
* instead, optionally send a separate confirmation email to the inquirer

* add some space between the button and the label

* they're not needed anymore since we switched to the generic
  notification builder in Invenio-Config-TUW

* enhance `babel.sh` script
* remove broken config items from `babel.ini`
* add translations entrypoint

* this uses some logic to determine if the "topic" record is published
  and available, and changes the endpoint to the deposit form if not

* this can happen for drafts, e.g. when "date" metadata fields aren't
  filled out which crashes with a `KeyError`

* also add a separate email that gets sent out to the uploader, to
  notify them that they have resubmitted their request and it needs to
  be reviewed again

* apparently, the `record` can be unset sometimes

* to give the users more information about the workflow

* add statement to clarify that the upload can now publish the dataset
  themselves

* if the changes are tracked as they are made, it's less likely that
  anything is missed on release and it's less tedious