* Ensure that tests will work in a virtual environment

* Fixes errors caught by pytest-black

* with 100x100 px
* exported as PNG with Inkscape directly from the corporate design SVG

* with transparent background
* and 1000x1000 px resolution

* Remove 'FAIR Data Austria' logo as it's not relevant anymore
* Revert to the layout for 4 logos
* Change dimensions of 'InvenioRDM' and 'FAIRSharing' logos to fit better in the footer according to the max thresholds

* this behavior can be controlled via a configuration flag
* it's disabled per default because it could be used to spam the inbox
  of arbitrary email addresses

* with a default of 5 attempts per hour
* this should be enough for legitimate requests, even with failed
  attempts (i.e. captcha mismatches) but still prevent spam floods
* also, hide the contact form for users when viewing their own records'
  landing pages

* use <pre> rather than <blockquote>, because the latter doesn't
  preserve newlines, etc. which may be unexpected given the textarea
  input

* Add FAIRsharing logo and adjust footer CSS grid

* escape the user-supplied values in the HTML email
* also, remove the whitespaces introduced by the license comments on top

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

* add *.jinja templates (for the email templates) to the MANIFEST.in

* this is possible since we configured sending of emails from the
  backend
* it replaces the current implementation of "contact uploader" that
  worked via "mailto" links, which was suboptimal because it exposes
  email addresses to the public
* it is also optionally protected via a captcha as a simple spam
  prevention mechanism that also prevents accidental resubmission of the
  form on refresh

* chase frontend build project changes in Invenio-Assets
* also many thanks to ULB Münster for the help here!

* because the changes have been merged upstream in Invenio-Previewer
  v1.3.9

* create a config item THEME_TUW_FRONTPAGE_INFO for the content
* add a block in the frontpage.html
* apply styling

* this has no business being hard-coded