Use release build for compliance tests?

[squell]

See the discussion at #892

This does require

• using RUSTFLAGS="-C debug-assertions -C overflow-checks"` at the release side.
• using the release Dockerfile to build "sudo under test".

Or can we omit the last step and observe that rustc produces the same binary in both cases?

This wasn't done earlier because the test-framework predates the release build framework.

[squell]

New idea: run compliance test on the release executable in the release workflow (now that we have a seperate release workflow). And leave the current debug build as is for regular compliance tests.

We should also consider future ideas for reducing binary size on the release, but that is a seperate (to be created) issue.