Turn off typechecking when called from exe

[gmcgibbon]

What are you trying to accomplish?

Some better typing, followed by disabling Sorbet when called from the executable / spring command.

What approach did you choose and why?

Type checking is useful, but I don't see use for it to be enabled in "production" use of the gem. When packwerk is validating or checking a codebase, type checking just slows it down and provides unhelpful errors to the user when something internal fails.

What should reviewers focus on?

Here's some benchmarks to compare runs on a huge app. I think this makes packwerk 20% faster.

• This branch
  • bundle exec packwerk check 79.08s user 23.77s system 298% cpu 34.415 total
  • bundle exec packwerk check 973.03s user 30.03s system 624% cpu 2:40.58 total (uncached)
• Main
  • bundle exec packwerk check 104.68s user 24.02s system 226% cpu 56.929 total
  • bundle exec packwerk check 1380.94s user 33.25s system 634% cpu 3:43.04 total (uncached)

Type of Change

• Bugfix
• New feature
• Non-breaking change (a change that doesn't alter functionality - i.e., code refactor, configs, etc.)

Additional Release Notes

• Breaking change (fix or feature that would cause existing functionality to change)

Include any notes here to include in the release description. For example, if you selected "breaking change" above, leave notes on how users can transition to this version.

If no additional notes are necessary, delete this section or leave it unchanged.

Checklist

• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• It is safe to rollback this change.

[alexevanczuk]

I just wish Sorbet had better support for turning off runtime type checking in production.

My ideal would be that you could use extend S::Sig (S for Static) which would add sigs that have no runtime component, and then in a test suite you could turn on runtime type checking. Stripe folks feel pretty strongly that runtime checking shouldn't be disabled though so I don't think it will happen.