ci(actions): trigger E2E tests on CircleCI manually from GitHub Actions

[jijiechen]

Checklist prior to review

• Link to relevant issue as well as docs and UI issues
  • N/A
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS
  • Confirmed
• Tests (Unit test, E2E tests, manual test on universal and k8s)
  • Manually tested
  • Don't forget ci/ labels to run additional/fewer tests
    • Added
• Do you need to update UPGRADE.md?
  • No need
• Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label)
  • No need

This PR adds the ability to trigger E2E tests on CircilCI manually from GitHub Actions.

[jijiechen]

I'll update the PR later based on the suggestions on the previous PR at #8424
You may review the content of this PR first. @lahabana

[lahabana]

The reason we don't use: https://github.com/CircleCI-Public/trigger-circleci-pipeline-action is that we can't pass params? I guess the problem with this is that we don't block until completion no?

[lahabana]

Maybe instead of having parameters to the circleci job we should just read https://github.com/CircleCI-Public/trigger-circleci-pipeline-action/tree/main#gha_meta in the circleCI job ?s

[jijiechen]

Right, we can't pass custom parameters using that action. That's why I call it manually. The GHA_Meta provides a way to pass custom parameters, we have to composite all params into one in this way, and we don't have a easy way to extract these params as part of the CircleCI workflow (using their setup job could be a way, that might require significant changes to the whole strcture).

In terms of blocking until completion, I believe that action does not provide this ability either. I read through the source code, and checkout of their readme, they are calling the same API with the one in my code and they only provide state of the just-created pipeline as an output as well.

For blocking until complete, we may laverage their other APIs to all workflows and periodically check latest state. Doc at https://circleci.com/docs/api/v2/index.html#operation/getWorkflowById