website: Bump prettier from 3.3.3 to 3.4.1 in /website (#12205)

* website: Bump prettier from 3.3.3 to 3.4.1 in /website

Bumps [prettier](https://github.com/prettier/prettier) from 3.3.3 to 3.4.1.
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prettier/prettier/compare/3.3.3...3.4.1)

---
updated-dependencies:
- dependency-name: prettier
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* update formatting

Signed-off-by: Jens Langhammer <jens@goauthentik.io>

* sigh

Signed-off-by: Jens Langhammer <jens@goauthentik.io>

* disable flaky test

Signed-off-by: Jens Langhammer <jens@goauthentik.io>

---------

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Jens Langhammer <jens@goauthentik.io>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Jens Langhammer <jens@goauthentik.io>

website/integrations/services/gitlab/index.md

@@ -21,8 +21,8 @@ In case something goes wrong with the configuration or you need to log in as adm
 
 There are 2 ways to configure single sign on (SSO) for GitLab:
 
--   [via SAML](#saml-auth)
--   [via OIDC Connect (OAuth)](#openid-connect-auth)
+- [via SAML](#saml-auth)
+- [via OIDC Connect (OAuth)](#openid-connect-auth)
 
 ### SAML auth
 
@@ -30,15 +30,15 @@ There are 2 ways to configure single sign on (SSO) for GitLab:
 
 The following placeholders will be used:
 
--   `gitlab.company` is the FQDN of the GitLab Install
--   `authentik.company` is the FQDN of the authentik Install
+- `gitlab.company` is the FQDN of the GitLab Install
+- `authentik.company` is the FQDN of the authentik Install
 
 Create an application in authentik and note the slug, as this will be used later. Create a SAML provider with the following parameters:
 
--   ACS URL: `https://gitlab.company/users/auth/saml/callback`
--   Audience: `https://gitlab.company`
--   Issuer: `https://gitlab.company`
--   Binding: `Redirect`
+- ACS URL: `https://gitlab.company/users/auth/saml/callback`
+- Audience: `https://gitlab.company`
+- Issuer: `https://gitlab.company`
+- Binding: `Redirect`
 
 Under _Advanced protocol settings_, set a certificate for _Signing Certificate_.
 
@@ -85,16 +85,16 @@ Afterwards, either run `gitlab-ctl reconfigure` if you're running GitLab Omnibus
 
 The following placeholders will be used:
 
--   `gitlab.company` is the FQDN of the GitLab Install
--   `authentik.company` is the FQDN of the authentik Install
+- `gitlab.company` is the FQDN of the GitLab Install
+- `authentik.company` is the FQDN of the authentik Install
 
 Create an application in authentik and note the slug, as this will be used later. Create a OAuth2 Provider with the following parameters:
 
--   Client type: `Confidential`
--   Redirect URI/Origins: `https://gitlab.company/users/auth/openid_connect/callback`
--   Scopes: `email`, `openid`, `profile`
--   Subject mode: `Based on the Users's Email`
--   Include claims in id_token: `True`
+- Client type: `Confidential`
+- Redirect URI/Origins: `https://gitlab.company/users/auth/openid_connect/callback`
+- Scopes: `email`, `openid`, `profile`
+- Subject mode: `Based on the Users's Email`
+- Include claims in id_token: `True`
 
 Under _Advanced protocol settings_, set a certificate for _Signing Certificate_.