feat(ci): introduce new release workflow (#2159)

> The Union mono-repo is made up of many different components that are
maintained and updated at different rates. We've opted to release
components individually rather than in all encompassing versions. To do
this, version tags are to now be made in the form of
`<component>-<semantic_version>` (`voyager-v0.2.1`). This will enable us
to quickly update and distribute various components without creating
monolithic releases.
> 
> Once a tag in the form of `<component>-<semantic_version>` is pushed
to the repo, the component in question will have a release triggered for
it from the "Release Component" workflow.
> 
> **NOTE**: The Release Component workflow needs to be updated to
introduce new components. See the workflow file in
`.github/workflows/release-component.yml` for more details.

Sample releases:
- [Voyager
0.1.0](https://github.com/unionlabs/voyager/releases/tag/v0.1.0)
- [uniond-release
test](https://github.com/unionlabs/uniond-release/releases/tag/test)

This effectively deprecates the previous release workflow, though we
will keep it around as a fallback for now.

The new workflow can be triggered by pushing tags in the form of
`<component>-<semantic_version>`. Currently the following products are
supported by the Release Component workflow:
-
[unionlabs/unionvisor-bundles](https://github.com/unionlabs/unionvisor-bundles)
-
[unionlabs/cometbls-light-client](https://github.com/unionlabs/cometbls-light-client)
- [unionlabs/ucs01-relay](https://github.com/unionlabs/ucs01-relay)
-
[unionlabs/uniond-release](https://github.com/unionlabs/uniond-release)
- [unionlabs/voyager](https://github.com/unionlabs/voyager)