[`semester-upkeep`] React based on Kaggle's API response

[jmuchovej]

NOTE: I'm still working on fleshing this one out, I've had to shift gears to other things – should be able to come back to this by Fri Dec 18.

• (🍜 Nice to Have) React based on the Kaggle API's response (it whines if you run more than 10 CPU Kernels or 2 GPU Kernels at a time)

Just a note, when referring to groups... groups := {intelligence, core, data-science, supplementary}

Feature Request, for autobot

Description Not all Kaggle Kernels need GPUs. More importantly, Kaggle limits us to 2 active GPU Kernels, while we're allowed up to 10 CPU Kernels. Based on this, it makes sense to toggle GPUs from syllabus.yml – this also allows for toggling the meeting's info if there's a need to rapidly iterate on the Kaggle Kernel.

Needs

• If a notebook fails to compile
• If a notebook fails to push because competition rules haven't been accepted,

Initial Comments

• Play around with the kaggle CLI and take a look at error codes. This should be a useful way to interpret whatever errors we have.