* because reindexing has been implemented in the core modules for a long
  time now

* we never used it anyway

* because we moved away from setuptools which had wrappers

* in hopes that publish failures will be less confusing from now on
* also, to detect errors (e.g. missing files in MANIFEST.in) earlier

* concentrate the configuration of all calls in one place

* 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