feat(core): add denyAccess api context to customJwt script

[simeng-li]

Summary

Add API context to the customJwt script payload, including the new denyAccess API.

• Only localVM environment jwtCustomizer is updated in this PR. Cloud azureFunction updates will be made in the cloud repo.

example:

const getCustomJwtClaims = async ({ token, context, environmentVariables, api }) => {
  api.denyAccess('You are not allowed to access this resource.');
};

Testing

test locally

Checklist

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

[github-actions]

COMPARE TO master

Total Size Diff 📈 +6.3 KB

Diff by File

Name	Diff
packages/core/src/libraries/jwt-customizer.ts	📈 +816 Bytes
packages/core/src/oidc/extra-token-claims.ts	📈 +690 Bytes
packages/core/src/routes/logto-config/jwt-customizer.ts	📈 +160 Bytes
packages/core/src/utils/custom-jwt/index.ts	📈 +1.57 KB
packages/integration-tests/src/mocks/jwt-customizer.ts	📈 +474 Bytes
packages/integration-tests/src/tests/api/logto-config.test.ts	📈 +1.28 KB
packages/schemas/src/types/logto-config/jwt-customizer.ts	📈 +1.37 KB