Create list of DevSecOps improvement/development guidelines for Tracker

[lcampbell2]

• TTL for branches: Ideal: 3 days, max 1 week
• TTL for PRs: Ideal: 0-1 days, max 3 business days
• Test coverage expectations: minimum 80 for all files in Stmts, Branch, Funcs, and Lines
• PR size expectations: reviewable within 1-2 hours
• Branch amount limits: Max 2 working feature branches, max 3 in-review branches
• Dependency updates: security bumps > Major bumps > minor bumps > patch bumps
• branch naming conventions: "feature/branch-name" or "bugfix/branch-name"
• PR naming conventions: see branch naming
• commit message conventions: should be concise, meaningful, and convey the purpose of the changes. A recommended convention is to use imperative language and start the message with a verb. For example, "Add user authentication feature" or "Fix bug in payment processing module." Additionally, including a reference to the associated issue or user story number in the commit message can provide better traceability.
• Code formatting: JS=prettier, python=black