…a-lux-form-identification="submitButton"

For some reason f:link.action does not work on every instance (but for sure on some). To prevent any errors we changed the links to f:be.link as it is done in newer versions of LUX anyway.

…ome bugfixes

Related: https://projekte.in2code.de/issues/62272

…e from local instance

So we now exclude all domains from all site configs in the where clause

Related: https://projekte.in2code.de/issues/62273

…download

Backported from commit 5af40d4

Related: https://projekte.in2code.de/issues/63177

and also reduce duplicate "last visit" to a "last visit" and a "first visit" column

Related: https://projekte.in2code.de/issues/63857

…st visit

Backport of commit 1b73c50

Related: https://projekte.in2code.de/issues/64460

Tracking purely based on device fingerprinting lead to some issues,
namely mobile browsers working more towards sandboxing requests so
that device hashes end up being the same across the same line of
devices. This makes individual tracking unreliable and in the case
of Lux leads to some leads that contain several different people
in them.

This change enriches the fingerprint with the users IP address
and hashes it again, leading to a more unique identification
value.

Negative impact of this change:
* (BREAKING) Previously identified users can't be identified anymore,
  as the calculated fingerprint value has changed.
* Compared to before, we now create _more_ unique users than before,
  as IP addresses (usually) change on the regular for home connections
  or when switching wi-fi/cellular networks.

Related: https://projekte.in2code.de/issues/67221