* these can happen if the error log file gets closed while the
  subprocesses are still writing to it, which can happen if the user
  aborts the execution with ^C

* this includes marking specific files as "safe"
* it can also be used to override the file format otherwise identified
  by siegfried

* in case the user hits ^C, skip the remaining files and store the
  results so far

* split the code into separate reusable modules
* add config files for linters & formatters
* force the progress bar to update after every sf run
* mask foot terminal as xterm for nicer progressbar output

* to ignore personalized files that would be built up over time by
  formatscaper

* also set it as default, because it's much faster and smaller than yaml

* this should help cut down runtime if there are large files involved
  (especially archives)

* remove the ETA, because that's never accurate anyway

* this is useful to see if the authentication and everything else works

* this is useful for local/development instances that have self-signed
  certificates and thus wouldn't pass the SSL check

* because they're ancient, and InvenioRDM has started providing version
  upgrade guides themselves since v1

* add script for fetching logs from the log server (OS)
* add golang-based program for calculating statistics from logs
* add README with more detailed information

* display the last parsed timestamp before the results, in addition to
  the start timestamp
* also fix the wrong timestamp being displayed as start date

* apparently, the file content would sometimes not be sent otherwise

* previously, the connection object could time out and cause issues
* also, include the error type in the message

* offers improved error handling
* should be more portable w.r.t. the execution environment

* add support for authentication tokens (required by InvenioRDM 1.0+)
* add switch to not publish created records