change(ci): When building crates individually, build all targets, and run clippy

[teor2345]

Motivation

There are some build failures that only show up when the tests are built in an individual crate. This impacts Zebra's usability for external developers.

This PR runs clippy and builds all targets in all crates individually. Then it fixes any errors that turn up.

This is related to #8019 and the scanner work in general, but these errors could happen in any crate.

PR Author Checklist

Check before marking the PR as ready for review:

• Will the PR name make sense to users?
• Does the PR have a priority label?
• Have you added or updated tests?
• Is the documentation up to date?

If a checkbox isn't relevant to the PR, mark it as done.

Solution

• Build all targets for individual crates, not just crates/binaries
• Run clippy on all targets for individual crates
• Use a medium runner because the zebrad test build takes more than 14 GB disk space
• Fix the build bugs that shows up:
  • Activate required features in test dependencies
  • Remove redundant test-only features in prod dependencies

Related cleanups:

• Standardise dependency order
• Remove unnecessary async in test functions

Admin:

• Add a branch protection rule for building zebra-scan individually

Testing

This PR fixes and adds tests.

Review

This is urgent because it will cause merge conflicts with upcoming changes.

Reviewer Checklist

Check before approving the PR:

• Does the PR scope match the ticket?
• Are there enough tests to make sure it works? Do the tests cover the PR motivation?
• Are all the PR blockers dealt with?
  PR blockers can be dealt with in new tickets or PRs.

And check the PR Author checklist is complete.

[oxarbitrage]

LGTM, thanks!