* because the 'rdm-records rebuild-index' command doesn't rebuild
  indices for all available/required services (at the moment)

* previously, adding files to drafts could fail if the configured limits
  (max. file size, and bucket quota) were too small for the files
* however, the main use for these CLI commands is to ingest files that
  are too large for self-upload via UI or API

* rename old 'orphans' subcommand for files to 'zombies'
* add new 'orphans' subcommand for files that operates on FileInstances
  which don't have any related ObjectVersions anymore

* use f-strings everywhere
* print error messages in yellow to stderr

* incorporate changes made to the service structure (all services
  attached to the record service)
* remove references to files-rest API where alternatives are available
* remove permission checks and as-user CLI option from some methods

* soft-deleted files will have ObjectVersions that don't have an
  associated FileInstance

* it seems that during deletion of drafts, the references to those files
  are deleted from the DB, but the files are still kept on disk
* thus, we now consider files to be orphaned that are still present in
  the file system, but don't have entries in the database anymore

* per default, try the more modern approach of updating the draft that
  is associated with the record's recid (service.update_draft() followed
  by service.publish()), and only in case of error fall back to
  service.update()
* add a "direct" variant of updating metadata, which circumvents the
  record service and directly modifies the record's metadata
* this is not recommended, but can come in handy when more direct access
  is required than the record service allows

* this new option allows dumping of the JSON data as stored in the
  database, rather than the record/draft projection

* make --as-user option not required anymore, use system identity per
  default

* use the new metadata schema for owners in the owner-setting feature
  when creating new records

* as fallback, the parameter --as-user/-u now reads its value from the
  environment variable INVENIO_UTILITIES_TUW_USER (if it is set)
* thus, the --as-user/-u parameter doesn't have to be specified for each
  command anymore
* the value is still required, s.t. either the env var or the CLI option
  have to be specified