chore(docs): Migrate from Docusaurus v2 to v3 (#8036)

Migrate Docs to latest version of Docusaursu (3.3.2 as of time of
writing)

---------

Co-authored-by: Florian Forster <[email protected]>

docs/docs/examples/identity-proxy/oauth2-proxy.md

@@ -21,7 +21,7 @@ We recommend that you use [Authorization Code](/apis/openidoauth/grant-types#aut
 
 A redirect URL is a URL in your application where ZITADEL redirects the user after they have authenticated. Set your url to the domain the proxy will be deployed to or use the default one `http://127.0.0.1:4180/oauth2/callback`.
 
-> If you are following along with the sample project you downloaded from our templates, you should set the Allowed Callback URL to <http://localhost:4200/auth/callback>. You will also have to set dev mode to `true` as this will enable unsecure http for the moment.
+> If you are following along with the sample project you downloaded from our templates, you should set the Allowed Callback URL to `http://localhost:4200/auth/callback`. You will also have to set dev mode to `true` as this will enable unsecure http for the moment.
 
 If you want to redirect the users back to a route on your application after they have logged out, add an optional redirect in the post redirectURI field.
 

docs/docs/examples/login/angular.md

@@ -25,7 +25,7 @@ We recommend that you use [Proof Key for Code Exchange (PKCE)](/apis/openidoauth
 The Redirect URIs field tells ZITADEL where it's allowed to redirect users after authentication. For development, you can set dev mode to `true` to enable insecure HTTP and redirect to a `localhost` URI.
 The Post-logout redirect send the users back to a route on your application after they have logged out.
 
-> If you are following along with the [example](https://github.com/zitadel/zitadel-angular), set the dev mode to `true`, the Redirect URIs to <http://localhost:4200/auth/callback> and Post redirect URI to <http://localhost:4200/signedout>.
+> If you are following along with the [example](https://github.com/zitadel/zitadel-angular), set the dev mode to `true`, the Redirect URIs to `http://localhost:4200/auth/callback` and Post redirect URI to `http://localhost:4200/signedout`.
 
 Continue and create the application.
 

docs/docs/examples/login/go.md

@@ -28,7 +28,7 @@ We recommend that you use [Proof Key for Code Exchange (PKCE)](/apis/openidoauth
 The Redirect URIs field tells ZITADEL where it's allowed to redirect users after authentication. For development, you can set dev mode to `true` to enable insecure HTTP and redirect to a `localhost` URI.
 The Post-logout redirect send the users back to a route on your application after they have logged out.
 
-> If you are following along with the [example](https://github.com/zitadel/zitadel-go), set the dev mode to `true`, the Redirect URIs to <http://localhost:8089/auth/callback> and Post-logout redirect URI to <http://localhost:8089/>.
+> If you are following along with the [example](https://github.com/zitadel/zitadel-go), set the dev mode to `true`, the Redirect URIs to `http://localhost:8089/auth/callback` and Post-logout redirect URI to [http://localhost:8089/](http://localhost:8089/)>.
 
 ![Create app in console - set redirectURI](/img/go/app-create-redirect.png)
 

docs/docs/examples/login/java-spring.md

@@ -162,7 +162,7 @@ java \
   -jar web/target/web-0.0.2-SNAPSHOT.jar
 ```
 
-If you then visit on <http://localhost:18080/webapp> you should directly be redirected to your ZITADEL instance.
+If you then visit on [http://localhost:18080/webapp](http://localhost:18080/webapp) you should directly be redirected to your ZITADEL instance.
 After login with your existing user you will be presented the profile page:
 
 ![Profile Page](/img/java-spring/app-profile.png)

docs/docs/examples/login/nextjs-b2b.md

@@ -22,7 +22,7 @@ First we need to create an organization that holds the Vendor's users, projects
 
 ### Vendor Organization
 
-Navigate to `https://{YourDomain}.zitadel.cloud/ui/console/orgs` (replace {YourDomain}), and click on the button "New".
+Navigate to `https://{YourDomain}.zitadel.cloud/ui/console/orgs` (replace \{YourDomain}), and click on the button "New".
 Toggle the setting "Use your personal account as organization owner".
 
 Enter the name `Demo-Vendor`, and click "Create". Then click on that organization.

docs/docs/examples/login/nextjs.md

@@ -41,7 +41,7 @@ Select `CODE` in the next step. This makes sure you still get a secret. Note tha
 
 With the Redirect URIs field, you tell ZITADEL where it is allowed to redirect users to after authentication. For development, you can set dev mode to `true` to enable insecure HTTP and redirect to a `localhost` URI.
 
-> If you are following along with the [example](https://github.com/zitadel/zitadel-angular), set dev mode to `true` and the Redirect URIs to <http://localhost:3000/api/auth/callback/zitadel>.
+> If you are following along with the [example](https://github.com/zitadel/zitadel-angular), set dev mode to `true` and the Redirect URIs to `http://localhost:3000/api/auth/callback/zitadel`.
 
 If you want to redirect the users back to a route on your application after they have logged out, add an optional redirect in the Post Logout URIs field.
 

docs/docs/examples/login/symfony.md

@@ -18,7 +18,7 @@ Before we can start building our application, we have to do a few configuration
 
 ### Project roles
 
-The Example expects [user roles](guides/integrate/retrieve-user-roles) to be returned after login.
+The Example expects [user roles](/docs/guides/integrate/retrieve-user-roles) to be returned after login.
 Symfony uses `ROLE_USER` format.
 The application will take care of upper-casing and prefixing for us.
 Inside ZITADEL, you can use regular lower-case role names without prefixes, if you prefer.