ci: setup miri

[seqre]

db and password_hash tests would not finish, investigating why can be a future endeavor

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Flag	Coverage Δ
rust	84.03% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
flareon-cli/tests/migration_generator.rs	100.00% <ø> (ø)
flareon-macros/src/dbtest.rs	92.85% <100.00%> (+0.12%)	⬆️
flareon-macros/tests/compile_tests.rs	100.00% <ø> (ø)
flareon/src/auth.rs	94.04% <ø> (ø)
flareon/src/auth/db.rs	76.66% <ø> (ø)
flareon/src/lib.rs	57.57% <ø> (ø)
flareon/src/static_files.rs	95.26% <ø> (ø)
flareon/tests/db.rs	98.66% <ø> (ø)
flareon/tests/flareon_project.rs	89.47% <ø> (ø)
flareon/tests/router.rs	93.61% <ø> (ø)

[m4tx]

It's kind of sad the tests are taking 8 minutes+ to run, but it is what it is, I guess. Hopefully they won't be too annoying, but given we don't use any unsafe code (for now), I would assume that if the normal tests pass, Miri tests will pass as well (except for the sqlite stuff, which is expected).

LGTM, but please address the comment in rust.yml.

[seqre]

It's kind of sad the tests are taking 8 minutes+ to run, but it is what it is, I guess. Hopefully they won't be too annoying, but given we don't use any unsafe code (for now), I would assume that if the normal tests pass, Miri tests will pass as well (except for the sqlite stuff, which is expected).

LGTM, but please address the comment in rust.yml.

@m4tx, I thought about reducing the number of times it runs, maybe just to tags, considering the type of testing it is. What do you think?

[m4tx]

@seqre I think we can keep it for pushes/PRs for now, as long as a) we don't require them to pass to merge PRs and b) we don't hit the GH Actions minute limit ah I think there's no limit for public repos. Let's see how annoying they actually are!