Add pre-commit hooks & BSD 3-Clause license

[amalnanavati]

Description

This PR adds pre-commit hooks to this repository. This ensures consistent formatting and style throughout the repository. After the PR gets merged in, I'll be able to configure this repository to automatically run the pre-commit hooks on every PR.

Related PRs:

• ada_ros2#51
• feeding_web_interface#150

Testing procedure

Although in theory this should not change any functionality, we must check. Thus:

• Start the demo in real: python3 src/ada_Feeding/start.py
• Eat a whole bite, verify everything works as expected.
• Start the demo in mock: python3 src/ada_Feeding/start.py --sim mock
• Go through a whole bite, verify everything works as expected.

Before opening a pull request

• pre-commit run --all-files
• Run your code through pylint. pylint --recursive=y --rcfile=.pylintrc .. All warnings but fixme must be addressed.

Before Merging

• Squash & Merge

[amalnanavati]

Note to reviewers: the main files to review are .pre-commit-config.yaml, the files in .github, and other new files. Other files were auto-modified by pre-commit hooks and have too many subtle spelling and formatting changes to reasonably review.

[jjaime2]

Seems good, just want to make sure our READMEs are still readable after this PR gets merged.

[jjaime2]

For this and others, are there any instances where our existing stack calls Python files with ./? My understanding is this would be the only reason to have the shebang line present, so I'm wondering if it was done intentionally. Anecdotally, I haven't seen any such cases, but it's good to double check.

[amalnanavati]

ROS uses it for running Python nodes, I think to allow developers to specify python2 vs python3.

[jjaime2]

Are the others besides ros2-devel intended to catch the names of the production branches in other repositories, i.e. this pre-commit workflow will be applied to them as well if these pre-commit files are copied over?

[amalnanavati]

Yup, I'll copy this directly into the other repos.

(I don't think additional branches should impact runtime, since this repo doesn't have branches by those names)

[amalnanavati]

Yes, my intent was to use this as a template for the other ADA repositories. I believe it doesn't add any extra computation to add these extra branches to the config file, since the branches don't exist.