Fix builds with slasher-redb

[michaelsproul]

Issue Addressed

Currently unstable fails to build with the slasher-redb feature due to a last-minute tweak I made to the redb impl prior to merging.

Proposed Changes

• Correct the compilation error
• Run the tests for the redb slasher on CI (would have caught this issue)

[jimmygchen]

Looks good to me!

[jimmygchen]

Oops, there's one failing slasher test: failed_override_with_existing_mdbx_db

[michaelsproul]

Deleted the failing test. It's a duplicate of another test with the same name failed_override_with_existing_mdbx_db which tests the case where you already have an MDBX database and start without MDBX enabled

[michaelsproul]

Ok third time lucky. Disabled all those slasher override tests when redb is involved.

[michaelsproul]

@mergify queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

The queue conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

[jimmygchen]

@mergify requeue

[mergify]

requeue

✅ This pull request will be re-embarked automatically

The followup queue command will be automatically executed to re-embark the pull request

[mergify]

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 7697c12