feat(info): add missing Dask, engine and session information

[Alputer]

Closes #163

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.40%. Comparing base (a8e3672) to head (b7e8357).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #164      +/-   ##
==========================================
+ Coverage   84.18%   84.40%   +0.21%     
==========================================
  Files          41       41              
  Lines        3542     3591      +49     
==========================================
+ Hits         2982     3031      +49     
  Misses        471      471              
  Partials       89       89              

Files with missing lines	Coverage Δ
cmd/info.go	92.50% <100.00%> (+5.17%)	⬆️

[tiborsimko]

You may want to amend the tests in order to have a case coverage for the new info endpoint replies? Right new we have:

• testdata/inputs/info_big.json
• testdata/inputs/info_empty_inactivity_period.json
• testdata/inputs/info_small.json

You could introduce the workfow engine ones into "big" example, and you could introduce a new info_dask.json example for Dask variables, since the new Dask feature is optional...

[tiborsimko]

question: ‏The textual output of the Python client and the Go client is the same, however the order of outputted information differs, for example:

$ rc info | tail -1
Yadage engine version: 0.20.1

$ rcg info | tail -1
The maximum number of workers that users can ask for the single Dask cluster: 20

Do we want to harmonise this at this time?

[tiborsimko]

question: ‏The JSON output of the Python client and the Go client differ with respect to null values:

$ rc info --json | jq > /tmp/z_py_j
$ rcg info --json | jq > /tmp/z_go_j
$ diff -u /tmp/z_py_j /tmp/z_go_j
--- /tmp/z_py_j 2025-01-21 13:46:00.209607732 +0100
+++ /tmp/z_go_j 2025-01-21 13:46:04.665618517 +0100
@@ -64,20 +64,17 @@
     "value": "False"
   },
   "kubernetes_max_memory_limit": {
-    "title": "Maximum allowed memory limit for Kubernetes jobs",
-    "value": null
+    "title": "Maximum allowed memory limit for Kubernetes jobs"
   },
   "maximum_interactive_session_inactivity_period": {
-    "title": "Maximum inactivity period in days before automatic closure of interactive sessions",
-    "value": null
+    "title": "Maximum inactivity period in days before automatic closure of interactive sessions"
   },
   "maximum_kubernetes_jobs_timeout": {
     "title": "Maximum timeout for Kubernetes jobs",
     "value": "1209600"
   },
   "maximum_workspace_retention_period": {
-    "title": "Maximum retention period in days for workspace files",
-    "value": null
+    "title": "Maximum retention period in days for workspace files"
   },
   "snakemake_engine_version": {
     "title": "Snakemake engine version",

Do we want to address this (admittedly minor) difference?

[tiborsimko]

todo: ‏For the commit log message, I would simply use

feat(info): print information about Dask and workflow engines  (#164)

Motivation: the "missing" is from the point of view of compatibility with the Python client, but it's just a matter of time that that one was implemented first. It could have been the other way round... So from the point of view of the release notes of the go client, this item was not really "missing" before, because we did not have any Dask at the time yet. Hence it's nicer to just say that this was added, but not that it was "missing".