APP-6990 consume debug level from cloud config

[abe-winter]

What changed

• consume debug field from cloud config, instead of only from CLI switch

Why

It's difficult to set this currently.

Notes

Where is the right place for this? I put it in the attributes for the viam-agent subsystem, but the map[string]DeviceSubsystemConfig approach seems less ergonomic post unification.

Manual test

With debug set to true:

2024-12-04T08:51:22.774Z INFO viam-agent viamserver/viamserver.go:183 viam-server started
2024-12-04T08:51:22.774Z DEBUG viam-agent agent/manager.go:277 starting background checks
2024-12-04T08:51:22.774Z DEBUG viam-agent agent/manager.go:185 Checking cloud for update
2024-12-04T08:51:22.882Z INFO rdk.package_manager packages/deferred_package_manager.go:143 cloud package manager created asyncronously

With debug set to false (second restart):

2024-12-04T08:51:28.572Z INFO viam-agent viamserver/viamserver.go:183 viam-server started
2024-12-04T08:51:28.654Z INFO rdk.package_manager packages/deferred_package_manager.go:143 cloud package manager created asyncronously

Sample config

{
  "agent": {
    "viam-agent": {
      "attributes": {"debug": true}
    }
}

[ale7714]

the logs around provisioning/network management will also be affected by this?

I think so bc we have globalLogger but making sure

[abe-winter]

the logs around provisioning/network management will also be affected by this?

yup, they showed up in my test:

2024-12-04T08:51:20.968Z DEBUG viam-agent provisioning/provisioning.go:73 Provisioning Config: &{Manufacturer:viam Model:custom FragmentID: HotspotInterface: HotspotPrefix:**** HotspotPassword:**** DisableDNSRedirect:false OfflineTimeout:120000000000 UserTimeout:300000000000 FallbackTimeout:600000000000 RoamingMode:false Networks:[] hotspotSSID: WifiPowerSave:}

[abe-winter]

(unless something is copying globalLogger before it sets debug, but it looks from grepping like this isn't happening)

[Otterverse]

One small nit, but otherwise looks fine!