Release Slicer v5.4

[jcfr]

Based on the state of the relevant sub-tasks, consider updating the issue description changing :question: (:question:) into either :hourglass: (:hourglass:) or :white_check_mark: (:white_check_mark:).

---

Checklist Installers Release:

• Pin this issue.
• ⌛ Finalize fixes related to failed extensions. See dashboard here.
• Announce release is in progress.
• Disable regular nightly builds.
• CMakeLists.txt: Update the Slicer version information for the release.
• Tag the repository with v5.4.0.
• CMakeLists.txt: Update the Slicer version information for the development.
• Create release 5.4.0 on slicer-packages.kitware.com.
• Tag and publish SlicerBuildEnvironment docker image.
• Create maintenance branch called 5.4 based on the first tag of the 5.4 series.
• Update readthedocs.
  • Activate the build of the 5.4 maintenance branch in readthedocs.
  • Add a Redirect of type Exact Redirects from /en/v5.4$rest to /en/5.4.
• Update release scripts.
• Update ExtensionsIndex by creating the 5.4 branch.
• Update CDash: Add Extensions-5.4-Nightly group to https://slicer.cdash.org/index.php?project=SlicerStable.
• Generate application and extension packages. See https://slicer.cdash.org/index.php?project=SlicerStable&date=2023-08-19.
  • Linux: ✅
  • macOS: ✅
  • Windows: ✅
• Update Release Details on the Slicer GitHub wiki.

---

Checklist Post Release:

These steps will take place in the week following Installers Release steps

• Re-enable regular nightly builds.
• Manually sign the packages.
  • Linux: NA
  • macOS: signed ✅, notarized ✅
  • Windows: ✅
• Upload signed release packages in the release folder.
  • Linux: NA
  • macOS: ✅
  • Windows: ✅
• In the 5.4.0 release folder, update each Slicer_<os>_<arch>_<revision> items changing the pre_release metadata from true to false.
  • Linux: ✅
  • macOS: ✅
  • Windows: ✅
• Update external websites.
• Update ExtensionStats module.
• Finalize Slicer Announcement.
• Publish Slicer Announcement & update discourse (draft here).
• Re-target unresolved GitHub issues.
• Unpin this issue.