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

@@ -12,13 +12,13 @@ Blueprints offer a new way to template, automate and distribute authentik config
 
 Blueprints are yaml files, whose format is described further in [File structure](./v1/structure). Blueprints can be applied in one of two ways:
 
--   As a Blueprint instance, which is a YAML file mounted into the authentik (worker) container. This file is read and applied regularly (every 60 minutes). Multiple instances can be created for a single blueprint file, and instances can be given context key:value attributes to configure the blueprint.
+- As a Blueprint instance, which is a YAML file mounted into the authentik (worker) container. This file is read and applied regularly (every 60 minutes). Multiple instances can be created for a single blueprint file, and instances can be given context key:value attributes to configure the blueprint.
 
     :::info
     Starting with authentik 2022.12.1, authentik watches for file modification/creation events in the blueprint directory and will automatically trigger a discovery when a new blueprint file is created, and trigger a blueprint apply when a file is modified.
     :::
 
--   As a Flow import, which is a YAML file uploaded via the Browser/API. This file is validated and applied directly after being uploaded, but is not further monitored/applied.
+- As a Flow import, which is a YAML file uploaded via the Browser/API. This file is validated and applied directly after being uploaded, but is not further monitored/applied.
 
 Starting with authentik 2022.8, blueprints are used to manage authentik default flows and other system objects. These blueprints can be disabled/replaced with custom blueprints in certain circumstances.
 
@@ -26,9 +26,9 @@ Starting with authentik 2022.8, blueprints are used to manage authentik default
 
 The authentik container by default looks for blueprints in `/blueprints`. Underneath this directory, there are a couple default subdirectories:
 
--   `/blueprints/default`: Default blueprints for default flows, tenants, etc
--   `/blueprints/example`: Example blueprints for common configurations and flows
--   `/blueprints/system`: System blueprints for authentik managed Property mappings, etc
+- `/blueprints/default`: Default blueprints for default flows, tenants, etc
+- `/blueprints/example`: Example blueprints for common configurations and flows
+- `/blueprints/system`: System blueprints for authentik managed Property mappings, etc
 
 Any additional `.yaml` file in `/blueprints` will be discovered and automatically instantiated, depending on their labels.
 

website/docs/customize/blueprints/v1/meta.md

@@ -10,7 +10,7 @@ See [examples](https://github.com/search?q=repo%3Agoauthentik%2Fauthentik+path%3
 
 #### Attributes
 
--   `identifiers`: Key-value attributes used to match the blueprint instance
+- `identifiers`: Key-value attributes used to match the blueprint instance
 
     Example:
 
@@ -20,6 +20,6 @@ See [examples](https://github.com/search?q=repo%3Agoauthentik%2Fauthentik+path%3
             name: Default - Password change flow
     ```
 
--   `required`: (Default: `true`) Configure if the blueprint instance must exist
+- `required`: (Default: `true`) Configure if the blueprint instance must exist
 
     If this is set to `true` and no blueprint instance matches the query above, an error will be thrown. Otherwise, execution will continue without applying anything extra.

website/docs/customize/blueprints/v1/tags.md

@@ -166,9 +166,9 @@ This tag takes 3 arguments:
 !Enumerate [<iterable>, <output_object_type>, <single_item_yaml>]
 ```
 
--   **iterable**: Any Python iterable or custom tag that resolves to such iterable
--   **output_object_type**: `SEQ` or `MAP`. Controls whether the returned YAML will be a mapping or a sequence.
--   **single_item_yaml**: The YAML to use to create a single entry in the output object
+- **iterable**: Any Python iterable or custom tag that resolves to such iterable
+- **output_object_type**: `SEQ` or `MAP`. Controls whether the returned YAML will be a mapping or a sequence.
+- **single_item_yaml**: The YAML to use to create a single entry in the output object
 
 2. `!Index` tag:
 
@@ -182,7 +182,7 @@ This tag takes 1 argument:
 !Index <depth>
 ```
 
--   **depth**: Must be >= 0. A depth of 0 refers to the `!Enumerate` tag this tag is located in. A depth of 1 refers to one `!Enumerate` tag above that (to be used when multiple `!Enumerate` tags are nested inside each other).
+- **depth**: Must be >= 0. A depth of 0 refers to the `!Enumerate` tag this tag is located in. A depth of 1 refers to one `!Enumerate` tag above that (to be used when multiple `!Enumerate` tags are nested inside each other).
 
 Accesses the `!Enumerate` tag's iterable and resolves to the index of the item currently being iterated (in case `!Enumerate` is iterating over a sequence), or the mapping key (in case `!Enumerate` is iterating over a mapping).
 
@@ -200,7 +200,7 @@ This tag takes 1 argument:
 !Value <depth>
 ```
 
--   **depth**: Must be >= 0. A depth of 0 refers to the `!Enumerate` tag this tag is located in. A depth of 1 refers to one `!Enumerate` tag above that (to be used when multiple `!Enumerate` tags are nested inside each other).
+- **depth**: Must be >= 0. A depth of 0 refers to the `!Enumerate` tag this tag is located in. A depth of 1 refers to one `!Enumerate` tag above that (to be used when multiple `!Enumerate` tags are nested inside each other).
 
 Accesses the `!Enumerate` tag's iterable and resolves to the value of the item currently being iterated.