feat(core): add DELETE /configs/jwt-customizer API

[darcyYe]

Summary

Add DELETE /configs/jwt-customizer/:tokenType API

Testing

Covered by unit tests and integration tests.

Checklist

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

[github-actions]

COMPARE TO master

Total Size Diff 📈 +2.32 KB

Diff by File

Name	Diff
packages/core/src/queries/logto-config.ts	📈 +53 Bytes
packages/core/src/routes/logto-config.openapi.json	📈 +588 Bytes
packages/core/src/routes/logto-config.test.ts	📈 +389 Bytes
packages/core/src/routes/logto-config.ts	📈 +584 Bytes
packages/integration-tests/src/api/logto-config.ts	📈 +164 Bytes
packages/integration-tests/src/tests/api/logto-config.test.ts	📈 +701 Bytes

[simeng-li]

overall LGTM

[wangsijie]

Can we set the token to nullable, then there is no need for "post" and "delete", just "put", if the user want to delete, he can pass { "token": null } to "put" payload

[darcyYe]

Can we set the token to nullable, then there is no need for "post" and "delete", just "put", if the user want to delete, he can pass { "token": null } to "put" payload

The whole JWT-customization-related data is stored as a record in our logto_configs table. Besides tokenSample we also have script (which refers to code snippets), envVars and contextSample (which is a user-customized context data sample for testing purpose). If the user deletes all these fields, we should delete the record if it is no longer used.