Removed federated connections tokens feature and ASN device binding option

BreakingBreaking change

This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.

What changed

Several previously documented features have been removed from the Auth0 Management API spec:

The ConnectionFederatedConnectionsAccessTokens schema and all federated_connections_access_tokens fields have been removed from Azure AD (v1/v2), Google Apps, and generic OAuth2/SAML connection options — clients writing this field will no longer have it accepted.
The FederatedConnectionTokenSet schema has been removed entirely.
The scopes read:federated_connections_tokens and delete:federated_connections_tokens have been removed from the API's scope list.
The asn enum value has been removed from ClientSessionTransferDelegationDeviceBindingEnum, making ip the only valid value; any client passing "asn" will now be sending an unsupported value.
All SDK code samples have been updated to require a domain/base_url parameter alongside token, which is an informational change to examples only.