Create coding practices SOP

[dfsnow]

Now that the Data Department is growing, we should create a short document outlining coding best practices in the office. This should include things like:

• Styling and tinting practices for different languages
• Pre-commit standards and practices
• Code review / PR practices
• Standards for setting user permissions

Steps:

• Move coding standards from handbook into separate SOP
• Update the onboarding issue template in ccao-data/people to include link to this standard

[dfsnow]

Per @jeancochrane, we should move to using Conventional Comments.

[dfsnow]

And we should stick to GH's branch naming convention: https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue#creating-a-branch-for-an-issue

[dfsnow]

Easy place to start: https://github.com/dsi-clinic/coding-standards

[dfsnow]

And another useful resource: https://github.blog/2023-08-04-a-checklist-and-guide-to-get-your-repository-collaboration-ready/

[dfsnow]

One more resource, per Jean: https://thoughtbot.com/playbook/developing/code-reviews

[dfsnow]

And one more: https://github.blog/2023-10-04-how-to-communicate-like-a-github-engineer-our-principles-practices-and-tools/

[dfsnow]

Thoughtbot guide to code review
Conventional comments
Leaving comments on your own pull requests
Internal PR example as an example of productive PR discussion