Update GitHub workflows

[bdemann]

• Make sure this stuff works on a release branch
• Make sure bash conditionals are correct and using the correct equality operator
• Update the ids of the final two tests in the yml and update the corresponding ids/names in github
• Make sure that the release tests test everything using the AZLE_TEST_RUN_ON_RELEASE env var
  • class_syntax/new
  • large_files
    • 250MiB
    • 1 GiB
    • 2 GiB
  • http_server/new
  • Additionally some are filtered entirely if we are on a release
    • examples/basic_bitcoin
    • examples/bitcoin_psbt
    • examples/ckbtc
    • tests/end_to_end/http_server/ethers_base
    • tests/end_to_end/http_server/http_outcall_fetch
    • tests/end_to_end/http_server/ic_evm_rpc
    • tests/property/candid_rpc/class_api/stable_b_tree_map
    • tests/property/candid_rpc/functional_api/stable_b_tree_map
  • My current thought is that these that are filtered we hope to one day run on regular tests but are too flaky. Meanwhile tests like new will only ever run on releases. So those are proper to have filtered in their package.json to denote the permanentality of their skipping except on release, right?

[lastmjs]

The algorithm is broken now for some reason, the algorithm to determine the paths