Release v0.2.4-rc.1

[robin-nitrokey]

This release candidate fixes concurrent access to different models and tests trusted publishing to PyPI.

[robin-nitrokey]

Looks like RPM does not like release candidates:

$ rpmspec -q --qf "%{version}" ci-scripts/linux/rpm/python3-nitrokey.spec
error: line 2: Illegal char '-' (0x2d) in: Version:        0.2.4-rc.1
error: query of specfile ci-scripts/linux/rpm/python3-nitrokey.spec failed, can't parse

The spec says:

The version string consists of alphanumeric characters, which can optionally be segmented with the separators ., _ and +, plus ~ and ^ (see below).
Tilde (~) can be used to force sorting lower than base (1.1~201601 < 1.1). Caret (^) can be used to force sorting higher than base (1.1^201601 > 1.1). These are useful for handling pre- and post-release versions, such as 1.0~rc1 and 2.0^a.

@mmerklinger Any objections to mapping vx.y.z-rc.n to x.y.z~rcn?

[robin-nitrokey]

Deployment does not work yet:

• The workflow is only triggered for released releases, not for prereleased releases.
• Even when marking the rc as a release, the filter github.event.name == 'release' is not active.