Migrate deployment to GitHub Actions and provide versioned builds

[FedeBev]

I would really appreciate if you could supply versioned assets.

In my opinion a non-versioned asset could not be considered production ready. In a production-ready configuration I must know which exact version of the UI I'm using in order to be able to handle any problems (#67 for example) upgrading or downgrading the UI, impossible operation right now.
We are building a cloud service based on clusters provided with rancher and hetzner cloud, we cannot have unmanageable problems, even if they are "only" of UI.

My proposal is to keep the master pipeline as is and create a pipeline for tags where the asset name contains the tag version; for example the asset URL for the v1.0.0 tag would be https://storage.googleapis.com/hcloud-rancher-v2-ui-driver/component_v1-0-0.js

[mxschmitt]

@FedeBev you are so right! Definitely have to add this.

[FedeBev]

Very glad you agree! Thanks!

[markusheinemann]

I can take care of this issue. How should versioning be handled? My proposal is to use a package like semantic-release which takes care of creating version tags, release notes and gh releases.

Which initial version number should be used?