ate-setup: save used settings locally after installation

[Steven Shriver (stshrive)]

This change wires a uniform configuration into the installer to enable saving the used setting to a local "cache" for later usage (i.e. during an upgrade).

All demos and install steps have been ported over to the uniform config file and commands will print their settings and the origin of those settings:

Example:

ATE_CREDENTIAL_PROVIDER='{"name":"k8s.io"}' bash hack/install-ate-kind.sh --deploy-ate-system
configuration: 7 set, 34 default
  ateapi.expectedJWTIssuer                    ""                   (from default)
  ateapi.postgres.cloudsql.gsa                ""                   (from default)
  ateapi.postgres.cloudsql.iamAuth            ""                   (from default)
  ateapi.postgres.cloudsql.instance           ""                   (from default)
  ateapi.postgres.cloudsql.ipType             ""                   (from default)
  ateapi.postgres.owner.connectionString      ""                   (from default)
  ateapi.postgres.owner.role                  substrate_owner      (from default)
  ateapi.postgres.poolMaxConns                ""                   (from default)
  ateapi.postgres.readWrite.connectionString  ""                   (from default)
  ateapi.postgres.readWrite.role              substrate_readwrite  (from default)
  ateapi.postgres.schema                      ""                   (from default)
  ateapi.postgres.serverCAFile                ""                   (from default)
  atenet.dataplane                            envoy                (from default)
  atenet.egress.additionalExtprocService      ""                   (from default)
  atenet.egress.credentialProvider            {"name":"k8s.io"}    (from ATE_CREDENTIAL_PROVIDER)
  benchmark.actorMemory                       ""                   (from default)
  benchmark.sandboxClass                      gvisor               (from default)
  benchmark.workerCount                       1                    (from default)
  clusterSize                                 size0                (from default)
  context                                     kind-kind            (from KUBECTL_CONTEXT)
  cordonControlPlane                          false                (from default)
  csi.setup                                   none                 (from --setup-csi)
  demo.anthropicAPIKey                        ""                   (from default)
  demo.counter.storageClass                   standard             (from default)
  demo.counter.withExternalVolume             false                (from default)
  gcp.clusterLocation                         ""                   (from default)
  gcp.clusterName                             ""                   (from default)
  gcp.projectID                               ""                   (from default)
  images.repo                                 ""                   (from default)
  images.tag                                  ""                   (from default)
  kindCluster.enabled                         true                 (from ATE_INSTALL_KIND)
  kindCluster.name                            kind                 (from default)
  ko.defaultPlatforms                         linux/amd64          (from KO_DEFAULTPLATFORMS)
  ko.dockerRepo                               localhost:5001       (from KO_DOCKER_REPO)
  kubeconfig                                  ""                   (from default)
  namespace                                   ate-system           (from default)
  otlpEndpoint                                ""                   (from default)
  podcert.workersPerSigner                    0                    (from default)
  record.dir                                  ""                   (from default)
  rolloutTimeout                              1m0s                 (from default)
  storage.bucketName                          ate-snapshots        (from BUCKET_NAME)

Breaking change

All in-flight API updates that are accessible via the ate-setup tooling must be updated to use the uniform config layer.

Fixes #1887

• Tests pass
• Appropriate changes to documentation are included in the PR

[Anna Pendleton (annapendleton)]

Non-blocking: changes like this are much easier to review in smaller pieces, e.g. (1) moving settings into the registry with no behaviour change, (2) the settings report, (3) saving runs. Not asking to split this one, just a thought for next time.

[Steven Shriver (stshrive)]

Non-blocking: changes like this are much easier to review in smaller pieces, e.g. (1) moving settings into the registry with no behaviour change, (2) the settings report, (3) saving runs. Not asking to split this one, just a thought for next time.

I generally agree. This was already broken down from the Config management aspect for that reason. My issue with breaking this down further is that API updates that change the underlying flags might get missed because adding them all to the config (change 1) before deleting them (change 2) leaves a chance for them to change at the source of truth until the wiring is complete (also Change 2) leading to regressions (added modified flag not in change 1). The issue I am facing now is that the merge conflicts are tripping me up a bit leaving behind some cruft. Not perfect either way

[Haven Xia (HavenXia)]

LGTM, thank you!