Tooling Improvements

[sgammon]

Summary

Adds more project documentation and prepares for full BCR support.

Constituent PRs

• Configure Renovate #8
• [StepSecurity] Apply security best practices #7

Task list

• Working Bzlmod sub-module test
• CI improvements
• Docs
  • DCO, CLA, PR template
  • Contribution guide
  • Security policy
  • README improvements
  • Copy-paste samples updated
  • Actions job for deploying docs site
• BCR Support
  • Config files for module publish
• Tooling
  • Dependency review
  • Support for Bazel CI
  • Dependabot
  • Renovate
  • CodeQL
  • OpenSSF Scorecard
  • Hardened CI
  • Linting
  • Support for full-blown integration tests note: next pr
  • Release flow for BCR

Changelog

• feat: add bazel ci presubmit
• test: run integration test for bzlmod in ci
• chore: add contribution guide
• chore: readme updates
• chore: doc link fixes
• chore: add CLA, DCO docs
• chore: add PR template
• chore: add dependency review config
• chore: drop outdated travis config
• chore: readme updates

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[alexeagle]

Hey, you should check out https://github.com/bazel-contrib/publish-to-bcr/ for the actual publish step, so that every release gets automatically published to the registry.

[sgammon]

@alexeagle heya :) will do -- should i set that up before i get approved on the BCR PR?

[alexeagle]

I generally do it from the beginning, following https://github.com/bazel-contrib/rules-template
If you do a manual publish, it's just delaying the release where you work out the automation.

[sgammon]

nice 👍🏻 caught me just in time, and on the perfect PR too. I'll add the .bcr configs and get the action going. I figured I'd have to be approved before I could push.