Consider creating a release with bundled livepeer-w3 after a tag push

A comment from @hjpotter92

> could go-tools generate a package similar to how studio releases livepeer-api and livepeer-www binaries with node dependencies bundled? it'd then simply be a matter of adding a service in manifest which can use the strip build target from this docker manifest.

If we follow that way, then we could re-use the `manifest.go` tool from `livepeer/catalyst` to build Docker images.

Start by reading the referenced manifest.go tool in livepeer/catalyst and the Docker manifest's strip build target. Determine how a tag push should produce a release containing livepeer-w3 with bundled node dependencies and expose it as a manifest service; done means the Docker image and release are generated through that flow.

Written by the indexing model from the issue text.