website/docs: ensure yaml code blocks have language tags (#9240)

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

website/docs/troubleshooting/emails.md

@@ -8,7 +8,7 @@ Some hosting providers block outgoing SMTP ports, in which case you'll have to h
 
 To test if an email stage, or the global email settings are configured correctly, you can run the following command:
 
-```
+```shell
 ak test_email <to address> [-S <stage name>]
 ```
 
@@ -16,12 +16,12 @@ If you omit the `-S` parameter, the email will be sent using the global settings
 
 To run this command with docker-compose, use
 
-```
+```shell
 docker compose exec worker ak test_email [...]
 ```
 
 To run this command with Kubernetes, use
 
-```
+```shell
 kubectl exec -it deployment/authentik-worker -c authentik -- ak test_email [...]
 ```

website/docs/troubleshooting/ldap_source.md

@@ -4,24 +4,24 @@ title: Troubleshooting LDAP Synchronization
 
 To troubleshoot LDAP sources, you can run the command below to run a synchronization in the foreground and see any errors or warnings that might happen directly
 
-```
+```shell
 docker compose run --rm worker ldap_sync *slug of the source*
 ```
 
 or, for Kubernetes, run
 
-```
+```shell
 kubectl exec -it deployment/authentik-worker -c authentik -- ak ldap_sync *slug of the source*
 ```
 
 Starting with authentik 2023.10, you can also run command below to explicitly check the connectivity to the configured LDAP Servers:
 
-```
+```shell
 docker compose run --rm worker ldap_check_connection *slug of the source*
 ```
 
 or, for Kubernetes, run
 
-```
+```shell
 kubectl exec -it deployment/authentik-worker -c authentik -- ak ldap_check_connection *slug of the source*
 ```

website/docs/troubleshooting/login.md

@@ -10,19 +10,19 @@ This recovery key will give whoever has the link direct access to your instances
 
 To create the key, run the following command:
 
-```
+```shell
 docker compose run --rm server create_recovery_key 10 akadmin
 ```
 
 For Kubernetes, run
 
-```
+```shell
 kubectl exec -it deployment/authentik-worker -c authentik -- ak create_recovery_key 10 akadmin
 ```
 
 or, for CLI, run
 
-```
+```shell
 ak create_recovery_key 10 akadmin
 ```
 

website/docs/troubleshooting/missing_admin_group.md

@@ -6,12 +6,12 @@ If all of the Admin groups have been deleted, or misconfigured during sync, you
 
 Run the following command, where _username_ is the user you want to add to the newly created group:
 
-```
+```shell
 docker compose run --rm server create_admin_group username
 ```
 
 or, for Kubernetes, run
 
-```
+```shell
 kubectl exec -it deployment/authentik-worker -c authentik -- ak create_admin_group username
 ```

website/docs/troubleshooting/missing_permission.md

@@ -8,13 +8,13 @@ The error should be temporary and not occur after initial installation.
 
 If it does, you can run the following command to ensure all permissions exist:
 
-```
+```shell
 docker compose run --rm worker repair_permissions
 ```
 
 or, for Kubernetes, run
 
-```
+```shell
 kubectl exec -it deployment/authentik-worker -c authentik -- ak repair_permissions
 ```