Revamp secrets manager to accept arbitrary objects

[daryllimyt]

Motivation

Support arbitrary auth schemas that will require more than just an api key or token. Simple example would be OIDC client ID and secret. We want a flexible + extensible schema that can support these.

Steps

• Get API keys to working state with the new schema feat(ui+engine): Extend secrets manager #36
  • Adjust secret hierarchy
  • Update frontend credentials settings page
  • Update frontend schemas to support fixed key-value pairs input of secret values. (Requires Create dynamic KV pair UI component #33 )
  • Update templated secrets parsing + test and verify that this works