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/xen-orchestra/index.md

@@ -22,8 +22,8 @@ If you are using the Xen Orchestra Appliance, the OIDC Plugin should be present.
 
 The following placeholders will be used:
 
--   `xenorchestra.company` is the FQDN of the Xen Orchestra instance.
--   `authentik.company` is the FQDN of the authentik install.
+- `xenorchestra.company` is the FQDN of the Xen Orchestra instance.
+- `authentik.company` is the FQDN of the authentik install.
 
 ## authentik configuration
 
@@ -31,10 +31,10 @@ The following placeholders will be used:
 
 Under _Providers_, create an OAuth2/OpenID provider with these settings:
 
--   Name: Provider for XenOrchestra
--   Authorization Flow: Select one of the available Flows.
--   Client type: Confidential
--   Redirect URIs/Origins: `https://xenorchestra.company/signin/oidc/callback`
+- Name: Provider for XenOrchestra
+- Authorization Flow: Select one of the available Flows.
+- Client type: Confidential
+- Redirect URIs/Origins: `https://xenorchestra.company/signin/oidc/callback`
 
 Take note of the Client ID and the Client Secret, because we need them for the configuration of Xen Orchestra.
 
@@ -42,9 +42,9 @@ Take note of the Client ID and the Client Secret, because we need them for the c
 
 Create an application with the following details:
 
--   Slug: `xenorchestra` (If you want to choose a different slug, your URLs for the Xen Orchestra Configuration may vary.)
--   Provider: Select the one we have created in Step 1
--   Set the Launch URL to `https://xenorchestra.company/`
+- Slug: `xenorchestra` (If you want to choose a different slug, your URLs for the Xen Orchestra Configuration may vary.)
+- Provider: Select the one we have created in Step 1
+- Set the Launch URL to `https://xenorchestra.company/`
 
 Optionally apply access restrictions to the application.
 
@@ -57,12 +57,12 @@ All of the URLs mentioned below can be copied & pasted from authentik (_Applicat
 2. Scroll to **auth-oidc** and click on the **+** icon on the right hand side.
 3. Configure the auth-oidc plugin with the following configuration values:
 
--   Set the `Auto-discovery URL` to `https://authentik.company/application/o/xenorchestra/.well-known/openid-configuration`.
--   Set the `Client identifier (key)` to the Client ID from your notes.
--   Set the `Client secret` to the Client Secret from your notes.
--   Check the `Fill information (optional)`-Checkbox to open the advanced menu.
--   Set the `Username field` to `username`
--   Set the `Scopes` to `openid profile email`
+- Set the `Auto-discovery URL` to `https://authentik.company/application/o/xenorchestra/.well-known/openid-configuration`.
+- Set the `Client identifier (key)` to the Client ID from your notes.
+- Set the `Client secret` to the Client Secret from your notes.
+- Check the `Fill information (optional)`-Checkbox to open the advanced menu.
+- Set the `Username field` to `username`
+- Set the `Scopes` to `openid profile email`
 
 4. Enable the `auth-oidc`-Plugin by toggling the switch above the configuration.
 5. You should be able to login with OIDC.