Automate deps lock updates

[srounce]

The deps-lock.json file should be regenerated whenever deps.edn changes, rather than being edited by hand. This commit avoids having to manually do this chore by regenerating deps-lock.json automatically and commiting it to you branch. This automation is in an effort to avoid contributors getting blocked due to confusing errors when deps-lock.json has either not been regenerated or edited by hand.

This also exposes clj-nix's deps-locktool in the nix devshell to make it easier for people to run it manually if they need to during development.

[KingMob]

Looks pretty cool. Can it detect if the deps-lock is out of sync, though, and skip making unneeded commits?

[srounce]

@KingMob if the content of deps-lock.json doesn't change as a result of the run then no commit will be created

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.89%. Comparing base (32adb67) to head (f67869c).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #96   +/-   ##
=======================================
  Coverage   75.89%   75.89%           
=======================================
  Files          30       30           
  Lines        1535     1535           
  Branches       64       64           
=======================================
  Hits         1165     1165           
  Misses        306      306           
  Partials       64       64           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ships]

i was prepared to merge this earlier but can't seem to get the required checks to run despite having hit "approve and run".

What is the necessary authority to run these checks?

I'll contact @srounce sidechannel about commit lint.

[KingMob]

@ships I authorized the checks to run. Hopefully it will do that in the future, for at least this PR.

[KingMob]

This looks blocked because the CI GH actions aren't running. I'm going to try to jump start it.

[KingMob]

@srounce Can you check that you got the invitation to join the OpenGen GH group? It still shows as pending, which might be why your GH Actions jobs aren't running. Not sure.

I tried seeing if I could forcibly restart your GH Actions, but I'm not seeing the relevant ones in the log anywhere.

Failing that, it may be necessary to reopen this PR from a branch of OpenGen/GenSQL.query itself, instead of your fork.