User/Group keys with dashes not included in schema

[TheRealFalcon]

Bug report

Due to some unfortunate old code, every users/groups key in our user data allows for both underscores and dashes. For example, if we define the key as ssh_authorized_keys, then ssh-authorized-keys is also valid.

The schema for all of the user and group properties contains the _ version of the key but not the - version. The schema needs to be updated to allow both while specifying that the - version is deprecated.

#5162 already does this for ssh-authorized-keys, but we should do it for the remaining keys to be consistent.

[afbjorklund]

The ca-certs was fixed earlier, but we weren't using schema back then so it was noticed and changed manually...

• commit af7eb1d

• Continue to honor deprecated config keys but emit DEPRECATION
  warnings in logs for continued use of the deprecated keys:
  • apt_sources key
  • any apt v1 or v2 keys
  • use or ca-certs or ca_certs.remove-defaults

    "cc_ca_certs": {
      "type": "object",
      "properties": {
        "ca_certs": {
          "$ref": "#/$defs/ca_certs.properties"
        },
        "ca-certs": {
          "allOf": [
            {
              "$ref": "#/$defs/ca_certs.properties"
            },
            {
              "deprecated": true,
              "deprecated_version": "22.3",
              "deprecated_description": "Use ``ca_certs`` instead."
            }
          ]
        }
      }
    },

• commit 6296124

[CalvoM]

Tracking at https://warthogs.atlassian.net/browse/SC-1777