Migrate Jenkins release build to GitHub Actions.

[rgrunber]

• Fixes Migrate Jenkins build to GH Actions for release #3059
  See https://github.com/rgrunber/vscode-openshift-tools/actions/runs/5804080228 for a sample of the build. It publishes a draft release at https://github.com/rgrunber/vscode-openshift-tools/releases/tag/1.6.0 (with the vsix artifacts included so they can be tested prior to approval) in addition to tagging the release.

• Is it worth adding the smoke tests ? They seem to be failing now.

• I have simplified some of the packaging logic, but it should behave the same, just less duplication of lines

• The TARGET=all was used to create a universal vsix that contained all of the tooling (and was also used in the smoke tests although maybe we could just use linux-x64 vsix for the smoke tests on ubuntu-latest). It was very large, and only used on OpenVSX. We removed it in Publish platform-specific VSIXs for OpenVSX. #2908. So we have no real reason to package it since we don't publish it anywhere.

• We aren't using pre-releases but I kept that input option in for potential future use.

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: -1.07% ⚠️

Comparison is base (7dccf83) 33.77% compared to head (48ed2a8) 32.71%.
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3089      +/-   ##
==========================================
- Coverage   33.77%   32.71%   -1.07%     
==========================================
  Files          73       74       +1     
  Lines        4755     4934     +179     
  Branches      907      940      +33     
==========================================
+ Hits         1606     1614       +8     
- Misses       3149     3320     +171     

see 6 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mohitsuman]

@rgrunber so once we start the action, it will ask for approval to publish to Marketplace, is that a notification based or we have to manually go in the action logs and approve it ?

[rgrunber]

@rgrunber so once we start the action, it will ask for approval to publish to Marketplace, is that a notification based or we have to manually go in the action logs and approve it ?

I didn't see anything in GH notifications but I did get an email with this :

[datho7561]

The unit test suite (npm run test) passes consistently. I think we can run it as a part of the release build.

This integration test suite is flaky, but we're working on fixing it:

• npm run public-ui-test

These integration test suites require an OpenShift cluster to run:

• npm run cluster-ui-test
• npm run test-integration

[datho7561]

Found a step we can probably skip, but other than that it seems good.

[datho7561]

Looks good to me!