Make sure that we can run locking on GitHub Actions

[krzysztofczyz-da]

This PR makes sure that we can verify the locker of scratchnets on GHA.

For context:

• as a part of porting infra_up I've ran into errors related to lock ownership
• in particular $SPLICE_ROOT/build-tools/approved-by.sh could not execute as the job did not have CCI token (and it does not make sense under GHA anyway)
• from a quick search it seems that the logic cannot really be replicated 1:1 under GHA as deployments don't have a direct API for this (unless we're speaking about approval from forks, than we have this endpoint)
• the closest thing would be a github actor (if we're talking about running workflows from GHA UI) or maybe custom deployment protection rule

Solution:

• since we're running those jobs manually anyway we can for sure just use GITHUB_ACTOR (or GITHUB_TRIGGERING_ACTOR)
• later on I'll change cluster_test (and others) to just print the cli command needed to run the workflow without doing any magic underneath which will be both simpler to understand and simpler to run
• CIRCLECI is always populated by CCI as you can see here, so no functionality is lost - tested with cluster_test on CCI side ✅

Refs:

• GITHUB_ACTIONS / GITHUB_ACTOR
• CCI env var

[krzysztofczyz-da]

/cluster_test

[github-actions]

Deploy cluster test triggered for Commit f70c859cbbc87ff505b13cfa71ce01974573ae34 in , please contact a Contributor to approve it in CircleCI: https://app.circleci.com/pipelines/github/DACH-NY/canton-network-internal/67311

[martinflorian-da]

Looks reasonable, thank you!

[martinflorian-da]

nit: consider making this local