Use Tracks in CI/CD

[amckinney]

All of the server-side components are in-place for release tracks, so we can turn our attention to tying it to a better CI/CD experience.

In short, when I push a GitHub branch, I want to see a release track with the same name in my BSR repository. This will help people iterate on a tighter feedback loop and give them access to BSR resources that would otherwise require a lot of manual processes (e.g. pushing to multiple BSR repositories).

[WillAbides]

I did some initial work on this creating a proof-of-concept workflow that pushes commits to a bsr track named for the current git branch and adds a commit status with a link to the bsr commit.

I am now working on tagging bsr commits with the corresponding git commit hash and handling instances where the same commit exists on multiple git branches.

[amckinney]

Tracks aren't relevant anymore, so we can close this one out.