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/docs/customize/brands.md

@@ -11,12 +11,12 @@ The main settings that brands influence are flows and branding.
 
 You can explicitly select, in your instance's Brand settings, the default flow to use for the following configurations:
 
--   Authentication flow: the flow used to authenticate users. If left empty, the first applicable flow sorted by the slug is used.
--   Invalidation flow: for typical use cases, select the `default-invalidation-flow` (Logout) flow. This flow logs the user out of authentik when the application session ends (user logs out of the app).
--   Recovery flow: if set, the user can access an option to recover their login credentials.
--   Unenrollment flow: if set, users are able to unenroll themselves using this flow. If no flow is set, option is not shown.
--   User settings flow: if set, users are able to configure details of their profile.
--   Device code flow: if set, the OAuth Device Code profile can be used, and the selected flow will be used to enter the code.
+- Authentication flow: the flow used to authenticate users. If left empty, the first applicable flow sorted by the slug is used.
+- Invalidation flow: for typical use cases, select the `default-invalidation-flow` (Logout) flow. This flow logs the user out of authentik when the application session ends (user logs out of the app).
+- Recovery flow: if set, the user can access an option to recover their login credentials.
+- Unenrollment flow: if set, users are able to unenroll themselves using this flow. If no flow is set, option is not shown.
+- User settings flow: if set, users are able to configure details of their profile.
+- Device code flow: if set, the OAuth Device Code profile can be used, and the selected flow will be used to enter the code.
 
 If a default flow is _not_ set in the brand, then authentik selects any flow that: