CodeQL CI automation - useful enough to burden CI runners?

[consideRatio]

We used this a while in various JupyterHub projects, but never got any concrete value from it, so we disabled it. Should we disable it here as well? So far, I have just seen it run silently and hogging CI runners.

By disabling CodeQL CI automation, we reduce energy footprint but and reduce the need to wait for avialable runners in a few cases when more than one thing is triggering workflow runs, like two PRs beign updated at the same time. The limit is 50 runners active at the same time, which we hit with 2 separate things being done in parallel.

For example right now, when pushing a tag and a commit to main, we provided two separate triggers, and ended up with jobs pending.

[consideRatio]

Action point: thumbs up to remove, comment to retain, then unassign yourself.

@andrius-puksta-sensmetry @simonas-drauksas-sensmetry @victor-linroth-sensmetry @vytautas-astrauskas-sensmetry

[andrius-puksta-sensmetry]

We could try adding a more aggressive config + custom .github/workflows/codeql-analysis.yml. Default config (as is now) enables only part of the checks (docs 1, docs 2).