Reorder the commit hooks by stack depth.

[stuhood]

Problem

There were two inversions in the commit hooks:

1. lint and style checks were running before semantic checks for python. If you experienced a mypy type error, you were likely to make changes that would break style. And broken style would cause a context switch before you were able to see whether you had fixed the semantic issue.
2. Likewise, python checks were occurring before rust checks: if the rust code was broken, you would need to re-compile it to run the python checks before being able to return to seeing whether you had fixed the semantic check.

These inversions can cause you to context switch between various tools to get back to the error you were trying to fix.

Solution

Re-order the hooks from bottom to top in terms of: 1) language (rust then python), 2) semantic level (semantic then stylistic).

[ci skip-rust-tests]
[ci skip-jvm-tests]

[Eric-Arellano]

Thank you! MyPy seems to be the thing that has issues the most frequently, so it will be wonderful to run that before running the headers check, for example.