CI: Add build-from-src-zip job

[mbien]

Build from src zip for release and platform in a separate job. This simplifies the platform job too as side effect.

Do we want to do this every time or only when certain labels are set? ( Platform [ci] enable platform tests (platform/*) , VSCode Extension [ci] enable VSCode Extension tests , ci:all-tests [ci] enable all tests and on master?)

this PR is intended to fail until #6583 made it back to master

[neilcsmith-net]

Yes, might not want to do this on every run.

We really need to have building the VSCode plugin tied in to the release cluster build here too. Given that's the failure that prompted this.

[mbien]

Yes, might not want to do this on every run.

yep, had the same thoughts

We really need to have building the VSCode plugin tied in to the release cluster build here too. Given that's the failure that prompted this.

this might be the missing puzzle piece:

  CLUSTER_CONFIG: ${{ (contains(github.event.pull_request.labels.*.name, 'rust') || github.event_name != 'pull_request') && 'full' || 'release' }}

we are so lucky that fake ternary ops work! We could build the full cluster only when rust is specified in PRs? What should happen on the master branch, post-merge?

edit: discussed this on slack a bit and we going to leave it on the full cluster config for now

[mbien]

well.. that job was supposed to fail. Lets stash this and try it plan b.

[mbien]

 BUILD FAILED
/home/runner/work/netbeans/netbeans/tmpbuild/java/java.lsp.server/build.xml:131: Cannot resolve rust.cargo. Neither one exist:
  /home/runner/work/netbeans/netbeans/tmpbuild/rust.cargo
  /home/runner/work/netbeans/netbeans/tmpbuild/rust/rust.cargo
Total time: 2 minutes 44 seconds
Error: Process completed with exit code 1.

it worked! success!

[neilcsmith-net]

Never been happier to see failing tests! 😄

[mbien]

rebased. should be green now if everything goes according to plan

edit: tests are green -> merging