Make JSON field name cases consistent

[aaron7]

We currently have a mixture of PascalCase, camelCase and snake_case.

Ideally all JSON field names should be camelCase, however depending on the API endpoint we are continuing to use what is already used for consistency.

It is unlikely we will be able to migrate to one format due to user hosted daemons and client side tools. However we may be able to migrate some WC specific apis and at least plan to use camelCase for all new endpoints.

[samb1729]

For reference, as of f9ff1ea69c, the following structs are used in api.UpstreamServer:

PascalCase (the default)

• v6.ImageStatus
• v6.ControllerStatus
• v6.Container
• v9.Change
• image.Info
• update.Cause
• update.ControllerResult
• update.ContainerUpdate
• update.ReleaseSpec
• update.Automated
• job.Status

camelCase

• v6.GitRemoteConfig
• v6.GitConfig
• ssh.Fingerprint
• ssh.PublicKey
• update.Spec
• job.Result
• policy.Update

[kingdonb]

Closing, this won't get fixed. Flux v1 is in Maintenance Mode (see #3320)