Build: Generate Release Artifact

[hborawski]

To avoid needing to commit generated files, like #67 we need to generate release artifacts instead of relying on the default .tar.gz that GItHub creates for each release.

The new artifact needs to contain all source code from the repository, in addition to generated files that rules rely on.

This artifact needs to be attached to the GitHub release which can be done with an auto plugin.

The local bazel-usage-note-auto-plugin for release notes will need to be updated to reflect the new archive location.

[sugarmanz]

This would also be a good opportunity to build the tools we produce to prevent the need for the consumers to build them. Ex:

rules_player/distribution/BUILD

Line 3 in 7a549a9

# TODO: We should probably build this for the archive