Add config information to router data model

[plorenz]

• Represent identity service configs in the persistence identity type, so we can easily grab them when they change. This also fixes a gap in auditing.
• Add identity service configs to to the rdm
• Add config types to the rdm
• Add configs to the rdm
• Add configs to services in the rdm

[qrkourier]

I'm imagining this leads to a hypothetical where some routers do not require pre configuration with a YAML file (out of band config), favoring an in band configuration managed centrally via client or ctrl plane, kicked off by enrollment.

For example,

1. Router finds client API via token issuer claim and verifies signature with server cert pubkey
2. Router finds ctrl plane in enrollment response and saves in local endpoints file
3. Router saves identity files in its working directory with default filenames, optionally configured by standard ziti env vars implemented in the create config subcommands

[plorenz]

I'm imagining this leads to a hypothetical where some routers do not require pre configuration with a YAML file (out of band config), favoring an in band configuration managed centrally via client or ctrl plane, kicked off by enrollment.

For example,

1. Router finds client API via token issuer claim and verifies signature with server cert pubkey

2. Router finds ctrl plane in enrollment response and saves in local endpoints file

3. Router saves identity files in its working directory with default filenames, optionally configured by standard ziti env vars implemented in the create config subcommands

The config here is service configurations, not router configuration. There is a desire for controller-provided router configuration, but that's not being addressed here.