website: bump prettier from 3.5.3 to 3.6.0 in /website (#15199)

* website: bump prettier from 3.5.3 to 3.6.0 in /website

Bumps [prettier](https://github.com/prettier/prettier) from 3.5.3 to 3.6.0.
- [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.5.3...3.6.0)

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

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

* format

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/add-secure-apps/providers/entra/add-entra-provider.md

@@ -19,11 +19,9 @@ As detailed in the steps below, when you add an Entra ID provider in authentik y
 2.  In the Admin interface, navigate to **Applications -> Providers**.
 3.  Click **Create**, and in the **New provider** box select **Microsoft Entra Provider** as the type and click **Next**.
 4.  Define the following fields:
-
     - **Name**: define a descriptive name, such as "Entra provider".
 
     - **Protocol settings**
-
         - **Client ID**: enter the Client ID that you [copied from your Entra app](./setup-entra.md).
         - **Client Secret**: enter the secret from Entra.
         - **Tenant ID**: enter the Tenant ID from Entra.
@@ -47,7 +45,6 @@ As detailed in the steps below, when you add an Entra ID provider in authentik y
 1. Log in as an admin to authentik, and go to the Admin interface.
 2. In the Admin interface, navigate to **Applications -> Applications**.
 3. Click **Create**, and define the following fields:
-
     - **Name**: provide a descriptive name.
     - **Slug**: enter the name of the app as you want it to appear in the URL.
     - **Group**: optionally, chose a group; apps in the same group are displayed together on the **My applications** page.

website/docs/add-secure-apps/providers/gws/add-gws-provider.md

@@ -20,11 +20,9 @@ When adding the Google Workspace provider in authentik, you must define the **Ba
 2. In the Admin interface, navigate to **Applications -> Providers**.
 
 3. Click **Create**, and select **Google Workspace Provider**, and in the **New provider** box, define the following fields:
-
     - **Name**: define a descriptive name, such as "GWS provider".
 
     - **Protocol settings**
-
         - **Credentials**: paste the contents of the JSON file you downloaded earlier.
         - **Delegated Subject**: enter the email address of the user all of authentik's actions should be delegated to
         - **Default group email domain**: enter a default domain which will be used to generate the domain for groups synced from authentik.
@@ -32,12 +30,10 @@ When adding the Google Workspace provider in authentik, you must define the **Ba
         - **Group deletion action**: determines what authentik will do when a group is deleted from authentik.
 
     - **User filtering**
-
         - **Exclude service accounts**: set whether to include or exclude service accounts.
         - **Group**: select any specific groups to enforce that filtering (for all actions) is done only for the selected groups.
 
     - **Attribute mapping**
-
         - **User Property Mappings**: select any applicable mappings, or use the default.
         - **Group Property Mappings**: select any applicable mappings, or use the default.
 
@@ -51,7 +47,6 @@ When adding the Google Workspace provider in authentik, you must define the **Ba
    If you have also configured Google Workspace to log in using authentik following [these](https://docs.goauthentik.io/integrations/services/google/index), then this configuration can be done on the same app by adding this new provider as a backchannel provider on the existing app instead of creating a new app.
    :::
 3. Click **Create**, and in the **New provider** box, and define the following fields:
-
     - **Slug**: enter the name of the app as you want it to appear in the URL.
     - **Provider**: when _not_ used in conjunction with the Google SAML configuration should be left empty.
     - **Backchannel Providers**: this field is required for Google Workspace. Select the name of the Google Workspace provider that you created in the steps above.

website/docs/add-secure-apps/providers/rac/how-to-rac.md

@@ -36,7 +36,6 @@ Next, you need to add property mappings for each remote machine you want to acce
 
 1. Log in to authentik as an administrator and open the authentik Admin interface.
 2. Navigate to **Customization > Property Mappings** and click **Create**.
-
     - **Select Type**: RAC Property Mappings
     - **Create RAC Property Mapping**:
         - **Name**s: define a name for the property mapping, perhaps include the type of connection (RDP, SSH, VNC)
@@ -61,7 +60,6 @@ Finally, you need to create an endpoint for each remote machine. Endpoints are d
 2. Navigate to **Applications > Providers**.
 3. Click the **Edit** button on the RAC provider that you previously created.
 4. On the Provider page, under **Endpoints**, click **Create**, and provide the following settings:
-
     - **Name**: define a name for the endpoint, perhaps include the type of connection (RDP, SSH, VNC).
     - **Protocol**: select the appropriate protocol.
     - **Host**: enter the host name or IP address of the remote machine.

website/docs/add-secure-apps/providers/rac/rac-public-key.md

@@ -53,7 +53,6 @@ SSH private keys can be configured via several methods:
 
 1.  Log in to authentik as an administrator, and open the authentik Admin interface.
 2.  Navigate to **Customization** > **Property Mappings** and click **Create**, then create a **RAC Provider Property Mapping** with the following settings:
-
     - **Name**: Choose a descriptive name
     - Under **Advanced Settings**:
         - **Expression**:
@@ -82,7 +81,6 @@ SSH private keys can be configured via several methods:
 
 1.  Log in to authentik as an administrator, and open the authentik Admin interface.
 2.  Navigate to **Customization** > **Property Mappings** and click **Create**. Create a **RAC Provider Property Mapping** with the following settings:
-
     - **Name**: Choose a descriptive name
     - Under **Advanced Settings**:
         - **Expression**:

website/docs/add-secure-apps/providers/ssf/create-ssf-provider.md

@@ -43,7 +43,6 @@ The workflow to implement an SSF provider as a [backchannel provider](../../appl
 2. Click **Create**.
 
 3. Define the settings for the application:
-
     - **Name**: define a descriptive name of the application.
     - **Slug**: optionally define the internal application name used in URLs.
     - **Group**: optionally select a group that you want to have access to this application.