[CI] Move tests from CircleCI to GitHub

[l0uden]

Description

Deleted .github/workflows/circleci-trigger.yml
Added:
.github/workflows/vizro-qa-notebooks-tests-trigger.yml - for triggering notebooks tests in vizro qa repo .github/workflows/vizro-qa-tests-trigger.yml - for triggering integration and screenshot tests in vizro qa repo

Connected with https://github.com/mckinsey/vizro-qa/pull/101

Screenshot

Notice

• I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

  • I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
  • I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorized to submit this contribution on behalf of the original creator(s) or their licensees.
  • I certify that the use of this contribution as authorized by the Apache 2.0 license does not violate the intellectual property rights of anyone else.
  • I have not referenced individuals, products or companies in any commits, directly or indirectly.
  • I have not added data or restricted code in any commits, directly or indirectly.

[antonymilne]

Looks great, thanks for making the changes and figuring out the matrix thing! ⭐

Just a few very minor comments but feel free to merge whenever you're ready.

[huong-li-nguyen]

Amazing job you guys! @l0uden @antonymilne

I have a couple of questions to the outcome itself. Feel free to merge though if not relevant for this PR:

1. I think we can remove the CircleCI test trigger as a required test in this PR now, right?

2. Instead of {{matrix.label}} - shouldn't there be a python version or whatever we have reserved for matrix.label? What is it for?

3. Just to clarify - do I understand correctly that Vizro QA notebooks tests trigger run the notebook test in our QA repo? And the Vizro QA integration tests trigger run the screenshot tests in our QA repo?

If yes, is there a way how we can actually add a link to the error message on where to find the failing screenshots tests? 😬 It doesn't have to be part of this PR, but I always have difficulties finding which run has failed in the QA repo and where I can find the failing screenshot tests since it doesn't run directly from here anymore.

Like somewhere here - adding a link to the the location of the failing screenshot tests or to the connected run on CircleCI?

[l0uden]

Amazing job you guys! @l0uden @antonymilne

I have a couple of questions to the outcome itself. Feel free to merge though if not relevant for this PR:

1. I think we can remove the CircleCI test trigger as a required test in this PR now, right?

2. Instead of {{matrix.label}} - shouldn't there be a python version or whatever we have reserved for matrix.label? What is it for?

3. Just to clarify - do I understand correctly that Vizro QA notebooks tests trigger run the notebook test in our QA repo? And the Vizro QA integration tests trigger run the screenshot tests in our QA repo?

If yes, is there a way how we can actually add a link to the error message on where to find the failing screenshots tests? 😬 It doesn't have to be part of this PR, but I always have difficulties finding which run has failed in the QA repo and where I can find the failing screenshot tests since it doesn't run directly from here anymore.

Like somewhere here - adding a link to the the location of the failing screenshot tests or to the connected run on CircleCI?

Thanks @huong-li-nguyen !

**1. Sure. I will do it after the merge

**2. When we're skipping tests the values from matrix can't be read. You can see the same picture for vizro-ai integration tests

**3. There's a chat with detailed information about all failing builds with links. I will add everyone to it after merging the PR