* use `hatchling` instead of `setuptools` as build tool
* remove `MANIFEST.in` since that's specific to setuptools
* also add `uv.lock` to gitignore

Update forms.py: change the consent message to: Allow the repository team to curate the metadata of my uploads after publication to facilitate long-term preservation

* the mappings have been fixed in invenio-communities v13.0.9

* based on what we have at Invenio-Theme-TUW

* based on what we already have at Invenio-Theme-TUW

* this eliminates a hacky use of a blueprint

* this hasn't been used ever since we switched over to curation reviews

* that's where most of the duplicates are coming from

* this should help with the elimination of duplicates

* fix preview permissions not granting access to the draft's files if
  they are restricted
* also refactor the permission levels for shared access (links & grants)
  to be easier to handle
* the latter unfortunately introduces duplicate generators in the policy
  and is thus a bit wasteful - if that turns out to be a problem, that
  should be updated in the future (e.g. via sets)

* removing this filter shows all drafts where the current user has
  access to rather than just their own drafts
* e.g. if a draft has been shared with a user, the recipient will now
  see them in their dashboard as well
* as a side effect, administrators will likely have all the drafts
  listed in their dashboard

* it looks like the extension may have been linked with issues regarding
  user-related operations such as login and file upload, so we decided
  to make it opt-in for now

* because golang apparently doens't play nice with the musl in alpine
  linux

* reduce the amount of data transferred for awkward spacing
* this should make dashes vs. no dashes in jinja constructs irrelevant
* static scripts and styling are already minified by the assets build
  and gets served by the reverse proxy anyway

* so that it's easier to get a working installation for tests

* through a service component, because the deposit form defaults would
  be set under `record.metadata.[...]` which is invalid
* the `access` API endpoint and the share modal only become active once
  the draft has been created, so the `create` hook should indeed be the
  first spot where the access settings are available

* because this request workflow can be used to evade our mandatory
  record review
* going through this config item seems to be the minimally invasive
  option (adding a custom requests service component may work better but
  also requires more maintenance)

* because I am impatient and don't want to wait until my upstream PR
  gets merged and released
* also, it's interesting to see how to override mappings

* follow naming from Invenio-Communities more closely
* also, remove some unused imports

* it's not really a new generator