Improve compilation and testing performance

[andrew-fleming]

Types of changes

What types of changes does your code introduce to OpenZeppelin Midnight Contracts?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Fixes #208.

PR Checklist

• I have read the Contributing Guide
• I have added tests that prove my fix is effective or that my feature works
• I have added documentation of new methods and any new behavior or changes to existing behavior
• CI Workflows Are Passing

This PR proposes to improve compile and testing performance.

• Compact compile accepts a directory arg that will only compile that directory
  • If that directory uses modules from security and/or utils, those modules will still be compiled first
• Turbo is better structured and runs in parallel. Most modules depend on security and/or utils, so those two modules are compiled first in parallel and then the other modules are compiled in parallel (or the modules of a single directory)
• Tests do not require the full build since they just need the used mock contracts' contract.cjs from artifacts. In other words, compiling with --skip-zk is sufficient to run tests

[emnul]

Need for speed!

[emnul]

Re-approve