Update documentation links and upgrade dependencies in package.json (#834)

* Update documentation links and upgrade dependencies in package.json

* Update documentation build process and dependencies

- Changed the documentation build command from npm to yarn for consistency.
- Added a new .nvmrc file specifying Node.js version 22 for the documentation environment.
- Updated the package.json to reflect the latest version of @docusaurus/module-type-aliases and increased the minimum required Node.js version to 20.0.

Author: danyi1212

Makefile

@@ -53,7 +53,7 @@ install-develop:
 
 # docs
 docs-dev:
-	@cd documentation && npm start
+	@cd documentation && yarn start
 
 # docker
 docker-build-client:

documentation/.nvmrc

@@ -0,0 +1 @@
+22

documentation/docs/getting-started/running-opal/run-opal-server/data-sources.mdx

@@ -79,7 +79,7 @@ Please be advised, this will not work so great in docker-compose. Docker compose
 
 For more dynamic cases where you'd need different clients to load different sets of data at different times;
 you can have the OPAL-clients be redirected to another server to fetch the configuration.
-See the [details in this tutorial](tutorials/configure_external_data_sources#how-to-configure-an-external-data-source)
+See the [details in this tutorial](/tutorials/configure_external_data_sources#how-to-configure-an-external-data-source)
 
 #### Security
 

documentation/docs/getting-started/tldr.mdx

@@ -17,7 +17,7 @@ Every time you push a change, the OPAL server will notify the subscribing OPAL-c
 
 OPAL tracks data from various sources via webhooks and [Fetch-Providers](/tutorials/write_your_own_fetch_provider) (extensible python modules that teach it to load data from sources).
 
-[Initial data is indicated by the server](getting-started/running-opal/run-opal-server/data-sources) based on `OPAL_DATA_CONFIG_SOURCES`.
+[Initial data is indicated by the server](/getting-started/running-opal/run-opal-server/data-sources) based on `OPAL_DATA_CONFIG_SOURCES`.
 Subsequent data updates are triggered via [the data update webhook](/tutorials/trigger_data_updates).
 Every time the policy agent (or it's managing OPAL-client) restarts, the data and policy are loaded from scratch.