feat: update config endpoints for use with providers

[lily-de]

One change that touched many files so it looks bigger than it is:

All pre-existing uses of set are now set_param and uses of get are get_param -- same function, just different name now

Before

• get(key) -- the config method to fetch a non-secret
• get_secret(key) -- the config method to fetch a secret
• set(key, value) -- the config method to set a non-secret
• set_secret(key, value) -- the config method to set a secret

After

• get_param(key) -- the config method to fetch a non-secret
• get_secret(key) -- the config method to fetch a secret
• set_param(key, value) -- the config method to set a non-secret
• set_secret(key, value) -- the config method to set a secret
• get(key, is_secret) -- the config method to fetch any key -- uses get_param and get_secret based on value of is_secret
• set(key, value, is_secret) -- the config method to get any key -- uses set_param and set_secret based on value of is_secret

Why?

• having a get function to always check all places for a secret makes it less complicated for the config endpoints that the frontend uses. we still never return the actual value of the secrets, but this way we have one method to call and it will handle the lookup or setting
• the frontend uses is_secret for setting and getting parameters a lot, so this creates parity as well

---

Rest of changes

1. Created an endpoint to return provider metadata and configuration state for each provider
2. Had to do some refactoring of the existing providers settings to handle the new datatype returned by the endpoint
3. Also had fix the page endlessly re-rendering and was suggested by goose to add some memo-ization

State of new settings at end of this PR:

• getting the provider information and state ✅
• we fetch the state and details about all providers from the backend, and now the frontend is using the same information as the cli
• note: we have to calculate 'is_configured' a bit differently than the cli because the cli checks the state of the provider's keys as the user goes through the configure flow. in the future we could refactor this so that there's shared functions between the two

Next:

• setting the provider information and state

[lily-de]

Added some more routes and schemas so openapi can create client-side functions for the UI to use to avoid needing to generate the types and client functions to call the backend.

[lily-de]

the real changes are here -- added an endpoint called providers which fetches provider metadata (name, description, keys etc) and if each provider is configured or not and returns that to the frontend

also updated other endpoints to verify that there's a secret key in the headers of the request for security -- this is something we do currently when fetching information on providers and extensions but we forgot to include it in the first iteration

[lily-de]

helper functions for the providers endpoint -- looks up information on if keys are set or not for the providers and determines if all required keys are set or not. will return key value in the response if not secret

[lily-de]

just renamed get to get_param and set to set_param

[lily-de]

Added the get(key, is_secret) and set(key, value, is_secret) methods and renamed the old get(key) and set(key, value) functions to get_param and set_param

[lily-de]

this file is auto-generated -- has the some updated information for the frontend on the different routes and schemas

[michaelneale]

yes looks like a big refactor!