see !2485

Revert 84d6ffee

Unfix #92

"Coordinator" is more appropriate inside Max Planck Society, but outside
of that "officier" is more common. Institutes can still call this group
whatever they want.

it's helpful to have these and there are no privacy concerns with
studies

Add recruitment consent history

See merge request !2512

rm eslint

See merge request !2534

eslint 9 has recently been released. It has several breaking changes,
especially with regards to configurations:
https://eslint.org/docs/latest/use/migrate-to-9.0.0

We have a tiny amount of js code when compared to python. eslint is
complex and slow and doesn't even find a lot of relevant issues. So I
don't think it is worth keeping it around.

Unfortunately I have not been able to find a decent replacement. But
given the tiny amount of JavaScript that we have, I think that is fine.

fix: do not delete study types when removing unnecessary recruitment attributes

See merge request !2533

This provides relevant context, e.g. when blocked subjects request to be
deleted.

There may be more static messages inside the content.
This way the temporary messages are not somewhere in the middle.

see https://github.com/docker/compose/issues/11628

Work on legal bases

See merge request !2532

There is validation to prevent this, but just to be sure.

see also db1b1629

only consider actual criteria for Participation.is_match

See merge request !2531

We already show warnings for the other filters (to be deleted, deceased,
blocked, privacy level). By lifting this restriction, we put more power
in the hands of recruiters. They control the machine instead of the
machine controlling them.

send notification when subject turns full age

See merge request !2519

tweak sessions end email

See merge request !2530

-   appointments are an optional feature, so we don't care whether they
    are correctly maintained
-   participations must be correctly maintained, otherwise it is
    impossible to e.g. access pseudonyms. SUggesting that users could
    let this slide and enter participants at the end of the study just
    incourages incorrect and potentially harmful usage.
-   Finishing a study and deleting its pseudonym lists is crucial for GDPR
    compliance because it removes the study as a legal basis.

https://github.com/dateutil/dateutil/blob/master/NEWS
https://github.com/jazzband/django-axes/blob/master/CHANGES.rst
https://alpinelinux.org/posts/Alpine-3.18.0-released.html