docs: Fix URL of CPU-usage (#6248)

README.md

@@ -362,7 +362,7 @@ This is how we create and publish a new release of the 121-platform.
 - Publish the release on GitHub (as 'latest', not 'pre-release')  
   This will trigger the deployment-workflow that can be monitored under [GitHub Action runs](/~https://github.com/global-121/121-platform/actions/workflows/deploy_staging_all.yml)
 - Check the deployed release on the staging-environment (_this can take some time..._)
-  - Now, and throughout the release process, it is wise to monitor the [combined CPU usage](https://portal.azure.com/#@rodekruis.onmicrosoft.com/blade/Microsoft_Azure_MonitoringMetrics/Metrics.ReactView/Referer/MetricsExplorer/ResourceId/%2Fsubscriptions%2Fb2d243bd-7fab-4a8a-8261-a725ee0e3b47%2FresourceGroups%2F510Global%2Fproviders%2Fmicrosoft.insights%2Fcomponents%2F121-global-application-insights/TimeContext/%7B%22relative%22%3A%7B%22duration%22%3A3600000%7D%2C%22showUTCTime%22%3Afalse%2C%22grain%22%3A1%7D/ChartDefinition/%7B%22v2charts%22%3A%5B%7B%22metrics%22%3A%5B%7B%22resourceMetadata%22%3A%7B%22id%22%3A%22%2Fsubscriptions%2Fb2d243bd-7fab-4a8a-8261-a725ee0e3b47%2FresourceGroups%2F510Global%2Fproviders%2Fmicrosoft.insights%2Fcomponents%2F121-global-application-insights%22%7D%2C%22name%22%3A%22performanceCounters%2FprocessorCpuPercentage%22%2C%22aggregationType%22%3A3%2C%22namespace%22%3A%22microsoft.insights%2Fcomponents%22%2C%22metricVisualization%22%3A%7B%22displayName%22%3A%22Processor%20time%22%2C%22color%22%3A%22%2347BDF5%22%7D%7D%5D%2C%22title%22%3A%22Most%20recent%20Max%20CPU%20usage%20App%20Services%22%2C%22titleKind%22%3A2%2C%22visualization%22%3A%7B%22chartType%22%3A2%2C%22legendVisualization%22%3A%7B%22isVisible%22%3Atrue%2C%22position%22%3A2%2C%22hideSubtitle%22%3Afalse%2C%22hideHoverCard%22%3Afalse%2C%22hideLabelNames%22%3Atrue%7D%2C%22axisVisualization%22%3A%7B%22x%22%3A%7B%22isVisible%22%3Atrue%2C%22axisType%22%3A2%7D%2C%22y%22%3A%7B%22isVisible%22%3Atrue%2C%22axisType%22%3A1%7D%7D%7D%7D%5D%7D) of our App-Services.
+  - Now, and throughout the release process, it is wise to monitor the [combined CPU usage](https://portal.azure.com/#view/Microsoft_Azure_MonitoringMetrics/Metrics.ReactView/ResourceId/%2Fsubscriptions%2Fb2d243bd-7fab-4a8a-8261-a725ee0e3b47%2FresourceGroups%2F510-121%2Fproviders%2FMicrosoft.Web%2FserverFarms%2F121/TimeContext~/%7B%22relative%22%3A%7B%22duration%22%3A172800000%7D%2C%22options%22%3A%7B%22grain%22%3A1%2C%22showUTCTime%22%3Afalse%7D%7D/Chart~/%7B%22metrics%22%3A%5B%7B%22resourceMetadata%22%3A%7B%22id%22%3A%22%2Fsubscriptions%2Fb2d243bd-7fab-4a8a-8261-a725ee0e3b47%2FresourceGroups%2F510-121%2Fproviders%2FMicrosoft.Web%2FserverFarms%2F121%22%7D%2C%22name%22%3A%22CpuPercentage%22%2C%22namespace%22%3A%22microsoft.web%2Fserverfarms%22%2C%22metricVisualization%22%3A%7B%22displayName%22%3A%22CPU%20Percentage%22%2C%22resourceDisplayName%22%3A%22121%22%7D%2C%22aggregationType%22%3A3%2C%22thresholds%22%3A%5B%5D%7D%2C%7B%22resourceMetadata%22%3A%7B%22id%22%3A%22%2Fsubscriptions%2Fb2d243bd-7fab-4a8a-8261-a725ee0e3b47%2FresourceGroups%2F510-121%2Fproviders%2FMicrosoft.Web%2FserverFarms%2F121%22%7D%2C%22name%22%3A%22MemoryPercentage%22%2C%22namespace%22%3A%22microsoft.web%2Fserverfarms%22%2C%22metricVisualization%22%3A%7B%22displayName%22%3A%22Memory%20Percentage%22%2C%22resourceDisplayName%22%3A%22121%22%7D%2C%22aggregationType%22%3A3%2C%22thresholds%22%3A%5B%5D%7D%5D%2C%22filterCollection%22%3A%7B%22filters%22%3A%5B%5D%7D%2C%22grouping%22%3Anull%2C%22visualization%22%3A%7B%22chartType%22%3A2%2C%22legendVisualization%22%3A%7B%22isVisible%22%3Atrue%2C%22position%22%3A2%2C%22hideSubtitle%22%3Afalse%2C%22hideHoverCard%22%3Afalse%2C%22hideLabelNames%22%3Atrue%7D%2C%22axisVisualization%22%3A%7B%22x%22%3A%7B%22isVisible%22%3Atrue%2C%22axisType%22%3A2%7D%2C%22y%22%3A%7B%22isVisible%22%3Atrue%2C%22axisType%22%3A1%7D%7D%2C%22disablePinning%22%3Atrue%7D%2C%22title%22%3A%22CPU%20%26%20Memory%20Usage%20App%20Service%20%20Plan%20121%22%2C%22titleKind%22%3A2%2C%22timespan%22%3A%7B%22relative%22%3A%7B%22duration%22%3A172800000%7D%2C%22showUTCTime%22%3Afalse%2C%22grain%22%3A1%7D%2C%22ariaLabel%22%3Anull%7D/openInEditMode~/true) of our App-Services.
 - If all looks fine, proceed with deploying the release to all other production-instances.
 - Make any configuration changes (`ENV`-variables, etc.) on each App-Service just before deployment.
 - Make any configuration changes for the Portal(s) in each [GitHub-environment-settings](/~https://github.com/global-121/121-platform/settings/environments).