## Description
numerous times lately I have pushed commits that break our linting (
typically the end of file new line ) but on occasion also spacing
changes. I've noticed others occasionally have the same issue. Setup a
pre-commit check that runs the same linting command that `uds run lint`
uses.

If lint is successful the commit is made, if lint failed commit is not
made and user is notified of what failed lint so they can fix. This also
only tests staged files.

Also could be built out a bit more to add restrictions to commit
messages and other things if we wanted, or even logic to run the
lint-fix ( which doesn't always work ).

## Type of change

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Other (security config, docs update, etc)

## Checklist before merging

- [x] Test, docs, adr added or updated as needed
- [x] [Contributor
Guide](https://github.com/defenseuni...