feat(schemas): update logto_configs table related types

[darcyYe]

Summary

We will support two custom JWT scenarios, AccessToken (for end-user) and ClientCredentials (for machine connection), Logto users can customize the logic to manipulate the raw token payload, and the result of the parsed token payload will be further processed by Logto OIDC service and then issued to the client.
For each scenario, Logto user can customize the token payload manipulation by providing a code snippet, env variables, and sample token/context (for testing purposes). This is a group of data that will be stored in logto_config table as a single DB record.

This PR is the preparation for upcoming custom JWT-related APIs, with the following update/refactor:

1. Enable new key column value LogtoJwtTokenKey for logto_config table.
2. For each LogtoJwtTokenKey, we provide the corresponding data guards (jwtCustomizerAccessTokenGuard and jwtCustomizerClientCredentialsGuard) and types (JwtCustomizerAccessToken and JwtCustomizerClientCredentials).

• All fields in data guards are optional to make the data flexible. Some fields have default values, but the backend does not care what the value is. The console will handle all of the value fallback logic.

Testing

N/A

Checklist

• .changeset
• unit tests
• integration tests
• necessary TSDoc comments

[github-actions]

COMPARE TO master

Total Size Diff 📈 +4.96 KB

Diff by File

Name	Diff
packages/schemas/src/types/index.ts	📈 +6 Bytes
packages/schemas/src/types/logto-config.ts	📈 +3.88 KB
packages/schemas/src/types/logto-config/index.ts	📈 +5.54 KB
packages/schemas/src/types/logto-config/oidc-provider.ts	📈 +3.29 KB

[wangsijie]

The token is just a simple string?

[simeng-li]

LGTM