Port drone build tasks to gh workflows + actions

[richard-cox]

Summary

Fixes #10633

Occurred changes and/or fixed issues

• Remove old drone build tasks (note - FOSSA will not be ported at this time, discussed in slack)
• create generic setup composit action which can be used by multiple workflows
• create generic lint, i18n-lint and unittest composit actions which can be used by multiple workflows
• create generic build-and-upload workflow which can be used by multiple workflows
• create workflow to trigger build-and-upload on merge to specific branch
• create workflow to trigger build-and-upload on specific tags

Also

• changed name of yarn target install:ci as it was used outside of ci

Note

• I'd have liked to group together the workflows used by the build, but things like workflow subfolders aren't supported

Examples

building from branch (with uploaded bits) - https://github.com/rancher/dashboard/actions/runs/8832322713
building from tag (with uploaded bit) - https://github.com/rancher/dashboard/actions/runs/8832309261

Technical notes summary

• branch builds aka 'hosted' builds provide a dist folder of the dashboard who's index.html is referenced in rancher setting ui-dashboard-index and used by rancher for the ui
  • hosted builds will also make the same output as embedded, this might be just for testing / validation
• tag builds aka 'embedded' builds provide a tar.gz of the dashboard build which is picked up by the rancher build, unpacked and embedded into it
  • embedded builds will also make the same output as hosted, this might be just for testing / validation
• rancher/ui pr - Port drone build tasks to gh workflows + actions ui#5140

Areas or cases that should be tested

• Validation of tar.gz on tag
• Validation of dist folder on branch
• Merges to master should upload to latest. Merges to other branches should upload to <branch name>
• Merges to only master, release-x or *-dev should trigger builds, no other

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

[nwmac]

LGTM