Add CI workflow

[huiwengoh]

• Add colab badge to every notebook
• Add CI workflow to lint notebooks to ensure correct kernel (for papermill), and that each notebook has a colab badge

Ref: https://github.com/cleanlab/examples/issues/12

[huiwengoh]

Rather than copy-pasting the nblint.py script from the cleanlab repo and modifying it, it would be nice to factor these out into a single place, so they stay in sync with each other / patches get applied to the common version / we can reuse code.

We could either make a GitHub action (little bit of extra boilerplate required, but then we can write stuff like uses: cleanlab/nblint in actions. Or we could just stick this in a common repo, like cleanlab-tools, and just fetch the file from the repo in each CI workflow.

Ah yes great point! Definitely agree that keeping everything in one place and in sync would be best practice.

I have no clue how to make custom GitHub actions, but am willing to invest some time learning if we think this is worthwhile, whereas I presume sticking the common code in a repo like cleanlab-tools would be a simpler task. I'm fine with either, do y'all have any opinions of which approach we should go with? @jwmueller @anishathalye

[anishathalye]

If we go with the GitHub action route: rather than having you learn it on your own, how about we pair program it together this weekend? (or before/after, over Zoom)

I think it's marginal extra effort to make it a GitHub action, btw.

[huiwengoh]

Yup that sounds good!

[huiwengoh]

Added CI for notebook linting, and colab badge + instructions to install requirements to every notebook!

Remaining TODOs:

• [x] verify that all links work
• [x] add note in DEVELOPMENT.md to discourage shifting the notebooks/file structure as it will break the links
• [x] https://github.com/cleanlab/nblint-action/pull/1 must be merge first, then change action call from a tagged version (current action is called from a branch)