DOC-377: Address review feedback on identity source docs

Move IsAuthorizedWithToken/BatchIsAuthorizedWithToken out of the
"when you create an identity source, LocalStack:" bullet list. Using
those APIs is a consequence of having a configured identity source,
not an action LocalStack performs at creation time.

Author: quetzalliwrites

src/content/docs/aws/services/verifiedpermissions.mdx

@@ -137,7 +137,8 @@ When you create an identity source with an [`OpenIdConnectConfiguration`](https:
 - Validates JWT signatures against the issuer's public keys
 - Enforces token expiration (`exp` claim)
 - Extracts principal information and group memberships from token claims
-- Evaluates authorization requests using [`IsAuthorizedWithToken`](https://docs.aws.amazon.com/verifiedpermissions/latest/apireference/API_IsAuthorizedWithToken.html) and [`BatchIsAuthorizedWithToken`](https://docs.aws.amazon.com/verifiedpermissions/latest/apireference/API_BatchIsAuthorizedWithToken.html)
+
+Once the identity source is configured, you can evaluate authorization requests using tokens from that provider with [`IsAuthorizedWithToken`](https://docs.aws.amazon.com/verifiedpermissions/latest/apireference/API_IsAuthorizedWithToken.html) and [`BatchIsAuthorizedWithToken`](https://docs.aws.amazon.com/verifiedpermissions/latest/apireference/API_BatchIsAuthorizedWithToken.html).
 
 :::note
 For local development scenarios where the OIDC issuer may not be reachable or uses a self-signed certificate, you can disable JWT signature verification by setting the `VERIFIEDPERMISSIONS_DISABLE_JWT_VERIFICATION=1` environment variable. See the [Configuration reference](/aws/customization/configuration-options/#verified-permissions) for details.