fix(dependencies): Update dcmjs library and improve documentation links (#4741)

platform/docs/docs/deployment/cors.md

@@ -43,7 +43,7 @@ The best alternative is to host OHIF over HTTPS.
 OHIF can be served over HTTPS in a variety of ways (these are just some examples).
 - Website hosting services that offer HTTPS deployment (e.g,. Netlify) or offer HTTPS load balancers (AWS, Google Cloud etc.)
 - Setting up a reverse proxy (e.g. `nginx`) with a self-signed certificate that forwards requests to the OHIF server
-    - [An OHIF Docker image can be set up this way](./docker.md#ssl).
+    - [An OHIF Docker image can be set up this way](./docker/docker.md#ssl).
 :::
 
 ## Origin Definition

platform/docs/docs/deployment/docker/docker.md

@@ -35,7 +35,7 @@ Building a Docker image comes in handy when OHIF has been customized (e.g. with
 
 ### Prerequisites
 The machine on which to build and run the Docker container must have:
-1. All of the [requirements](./build-for-production.md#build-for-production) for building a production version of OHIF.
+1. All of the [requirements](../build-for-production.md#build-for-production) for building a production version of OHIF.
 2. A checked out branch of the OHIF Viewer.
 3. [Docker](https://docs.docker.com/get-docker/) installed.