Updating workflow to use Github CPU runner

[ericspod]

Fixes #2031.

Description

This will change the failing CICD check to use Github CPU runners.

Checks

• Avoid including large-size files in the PR.
• Clean up long text outputs from code cells in the notebook.
• For security purposes, please check the contents and remove any sensitive info such as user names and private key.
• Ensure (1) hyperlinks and markdown anchors are working (2) use relative paths for tutorial repo files (3) put figure and graphs in the ./figure folder
• Notebook runs automatically ./runner.sh -t <path to .ipynb file>

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[ericspod]

Hi @KumoLiu this is the solution I think for getting the tests running again using CPU runners. One issue that we'll find is notebooks will have to run under CPU, some will be very slow as a result plus many in the repo which were tested with GPU cannot be retested now. We can make this change now to put through the PRs we have waiting, or we can change branch rules to allow repo owners to circumvent stuck tests. Thoughts?

[KumoLiu]

We can make this change now to put through the PRs we have waiting, or we can change branch rules to allow repo owners to circumvent stuck tests. Thoughts?

Hi @ericspod, yes. we can merge this one now to put through the PRs we have waiting and also let me change the premerge-notebools as a not "required" check, then if there are some tests must be runned on the GPU, the PR will not stuck as well. What do you think?