SCIM doc updates (#3229)

* Update known limitations for SCIM for Entra

Author: aneita-octo

src/pages/docs/security/authentication/scim/configuring-microsoft-entra.mdx

@@ -179,4 +179,3 @@ Entra ID will now reach out to Octopus Deploy regularly via the SCIM API wheneve
 - Octopus Deploy does not support nested groups. Any requests from Entra ID to add a group as a member of another group will be ignored.
 - Any groups provisioned by Entra ID will be global teams, rather than space-scoped teams, because Azure AD authentication applies to the whole Octopus Deploy instance. You can still apply space-scoped permissions to these teams, but the teams will be visible to all spaces.
 - Octopus Deploy only supports a single email address for each user, whereas Entra ID supports many. Octopus Deploy will ignore any email addresses other than the **Work** email address, ie: `emails[type eq "work"].value`.
-- Entra ID has a [Provisioning Expression builder](https://learn.microsoft.com/en-us/entra/identity/app-provisioning/expression-builder) feature in preview, which depends on APIs that are not yet implemented in Octopus Deploy. As such, you may see errors if you try to use the Provisioning Expression builder in the Azure Portal.