* so that reviewers know that somebody has started looking at the record
  and can remove it from their (mental) TODO list

* the "metadata" service component copies over every field *except for*
  "version" and "publication_date" from the old record

* missing version fields are handled by the UIJSONSerializer by
  constructing a string of the shape "v{version_index}"
* the "metadata" service component removes both the "version" and
  "publication_date" fields from new versions of records
* experience shows that users rarely put in explicit values for the
  version field, which creates inconsistency

* with the new rdm-curation workflow, community-submission requests
  cannot be used to circumvent our mandatory reviews anymore
* also, they have been requested as a feature

* previously, this property was missing from the fake entity which would
  trip up notification builders

* setting an empty value in the settings form previously caused a
  validation error because the empty string is not a valid email address

* previously, i forgot to override that configuration item after
  calculating its value
* if not set as configuration explicitly, Invenio-RDM-Records would then
  set a default value of "127.0.0.1:5000" for it

* because Invenio-App-RDM sets a default value for that config item
  mismatching our setup

* Invenio-Config already takes care of checking the value in real
  Invenio applications and issues a warning if it's unset

* `tuw_config` is a bit nicer than `zzz_invenio_config_tuw`, and should
  still be the last entry in the list considering the usual naming
  scheme

* previously, our configuration magic was performed as part of the
  `finalize_app` entrypoint
* while this worked well enough for most use cases, some extensions
  would break this model by caching values during their initialization
* especially caching-related extensions like to take eagerly create
  clients with the current configuration items, which are hard to fix
  afterwards
* keeping track of all the instantiated clients just to change their
  connection details when we perform our magic really didn't seem like
  a good approach
* so instead, we now made sure that our extension is loaded first and
  can thus perform its configuration magic before any other extension
  has a chance of caching values
* also, extension loading happens after the configuration loading is
  done (especially the handling of environment variables)

* since we're not quite ready for matrix notifications yet, this wasn't
  supposed to be added to the code

* add functionality to assemble some config items (like the DB
  connection string) from their parts
* this was previously implemented in our `invenio.cfg`, but more flaky
  because it had to deal with parsing and setting environment variables
* also refactor the startup module

* sometimes the cleanup operations for failed file uploads seem to leave
  over some `FileInstance` entries in the database that have a null URI
* these file instances cause the periodic health checks to fail and
  trigger warning emails

* this enables users to set an alternative email address to which
  notifications will be sent, in case they don't like to use their
  institutional email address

* this can be very useful for having a single project that is used for
  both "local" and "containerized" execution, where some configuration
  items should be slightly different for either (e.g. `SEARCH_HOSTS`)
* currently we have this functionality implemented in our `invenio.cfg`
  but there it is a bit awkward due to the fact that environment
  variables have not been translated into `app.config` yet

* this brings it more in line with the request notifications
* previously we were restricted to emails, now it will be whatever
  notification backends we use
* also remove the mail templates - they now live in code until we
  enhance the notification backend to be more flexible w.r.t. the
  rendered templates

* previously, the global was still set to the original Flask config
  which may not be in sync with the overridden config and thus cause
  unexpected behavior

* fix links being formatted in MD rather than reST
* mention the new submission review workflow, notification backends, and
  background tasks

* this makes sure that our custom translations will be picked up, if we
  ever go for translations

* forward extra arguments to pybabel
* add missing fixed argument to "extract"
* provide better usage information

* they're now built into the compiler:
  https://jinja.palletsprojects.com/en/stable/changes/#version-3-0-0

* because otherwise, `url_for()` will prefer that value over the HTTP
  Host header value
* this causes issues for us with our multi-domain setup, in conjunction
  with the OIDC redirects - given that `SERVER_NAME` can only be a
  scalar value, trying to login on a secondary domain will redirect to
  the primary one and typically fail (because sessions are different, etc.)
* also make sure that the `APP_ALLOWED_HOSTS` config contains the
  `SERVER_NAME` if set

* apparently it was a leftover `before_first_request` handler
* reworked it as `finalize_app` entrypoint
* also, added a check if the app config is already a TUW config to avoid
  unnecessary nesting

* to fix our multi-domain setup with Flask 2.x and 3.0
* see: https://github.com/pallets/flask/pull/5634
* this can be removed once we get Flask 3.1+ in

* create dedicated modules for curations & notifications to separate the
  general notifications infrastructure from the curations-related parts
  (and requests)
* split large modules into smaller logical groups
* split tasks.py into three separate parts: curations, TISS, and general

* automatic accept of submissions for the test system
* reminder for uploaders about accepted but still unpublished records
* reminder for reviewers about open curation requests