fix(staticwado): SM and RT and update the server with new data (#3422)

* fix bugs for the RT for the new demo

* fix SM with the static-wado server

* remove thumbnail from tmtv

* migration guide

* fix stability for the rt struct

* apply review comments

* add loading indicator to SM

* pdf works

* try to fix relative bulkData

* fix the rest

* fix preflight for the SM

* fix typo

* apply review comments

* yarn lock

platform/docs/docs/configuration/dataSources/dicom-web.md

@@ -179,6 +179,24 @@ See the [`singlepart`](#singlepart) data source configuration option.
 ### DICOM Video
 See the [`singlepart`](#singlepart) data source configuration option.
 
+### BulkDataURI
+
+The `bulkDataURI` configuration option allows the datasource to use the
+bulkdata end points for retrieving metadata if originally was not included in the
+response from the server. This is useful for the metadata information that
+are big and can/should be retrieved in a separate request. In case the bulkData URI
+is relative (instead of absolute) the `relativeResolution` option can be used to
+specify the resolution of the relative URI. The possible values are `studies`, `series` and `instances`.
+Certainly the knowledge of how the server is configured is required to use this option.
+
+```js
+bulkDataURI: {
+  enabled: true,
+  relativeResolution: 'series',
+},
+```
+
+
 ### Running DCM4CHEE
 
 dcm4che is a collection of open source applications for healthcare enterprise

platform/docs/docs/migration-guide.md

@@ -209,6 +209,13 @@ see [custom routes](./platform/services/ui/customization-service.md#customroutes
 </details>
 
 
+## DICOM Endpoints
+
+In OHIF v3 there is a new end point that your DICOM server should be able to respond to
+`WADO-RS GET studies/{studyInstanceUid}/series`
+
+This is used in the viewer for fetching the series list for a study to use for the hanging protocol.
+
 ## LifeCycle Hooks
 
 OHIF v2 had `preRegistration` hook for extensions for initialization. In OHIF v3 you have

platform/docs/docs/platform/services/ui/customization-service.md

@@ -490,7 +490,7 @@ are specific to the context used for where the menu is displayed.
 The default cornerstone context menu can be customized by setting the
 `cornerstoneContextMenu`.  For a full example, see `findingsContextMenu`.
 
-## Customizeable Cornerstone Viewport Click Behaviour
+## Customizable Cornerstone Viewport Click Behaviour
 
 The behaviour on clicking on the cornerstone viewport can be customized
 by setting the `cornerstoneViewportClickCommands`.  This is intended to