perform iso5 release

[sanderr]

Things that need to go in after RC1

• all those for ISO4.4.1(https://github.com/inmanta/irt/issues/1002)
• Issue/3789 symmetric increments (#3790) #3792 -> merged
• Project install use server env vars pytest-inmanta-lsm#184 -> ongoing
• Issue/178 project install pytest-inmanta-lsm#182 -> merged
• Improve error reporting on invalid V2 Modules #3797 / Improved error message #3799 -> ongoing

TODO

• (Issue/795 configurable autodeploy #947) Perform a patch release for all modules with unreleased dependency updates.
• Ensure that the compiler version (src/inmanta/__init.py__) has been bumped since the last release or no improvements
  have been made to the compiler since.
• A database dump of the current version is included in the tests/db/dumps directory, along with a test that verifies
  the migration (on inmanta-core and inmanta-lsm).
• run RC release job
• build npm packages (build only!)
  • dashboard
  • web-console
• run next build
• run next build documentation
• Run the RC tests
  • Quickstart-lsm (manual: See ISO product documentation under Module guides -> LSM module -> LSM quickstart)
  • Performance test (automated)
  • Compiler scaling (automated)
  • Modulesets (automated)
  • UC1 (ask Bart)
  • UC2 (ask Wouter)
  • CBCI (ask Bart)
  • Verify that the next release of the documentation looks ok (See: https://docs.inmanta.com/inmanta-service-orchestrator-next//)
• run project invariant check to guard against patching mistakes
• run stable release job
• build npm packages (build only!), might have been built and published already if there are aligned branches.
  • dashboard
  • web-console
• run stable build
• run stable build documentation
• release module set
• inform marketing people

After major release

• Make sure https://docs.inmanta.com/inmanta-service-orchestrator/ redirects to the newly released version.
• Mention the new major release on the website https://inmanta.com/resources/docs/ (Ask Wouter or Bart)
• Set up dependabot for the new branches: on master, update the config to enable dependabot updates for master and the newly
  created named iso branch. Disable it for the previously listed iso branch because that one should only receive security
  updates (inmanta/irt#512). Merge the config change using the merge tool, which acts as a guard against accidental branch
  divergence.
• Update the following pipelines to run against the newly released version:
  • pytest-inmanta-lsm
  • vscode-inmanta
  • inmanta-sphinx
  • docker-pytest
• Update the traffic light config in the infra model to include the newly created named iso branches for all relevant
  pipelines. Disable traffic light reporting for iso versions support was dropped for, if any.
• Update the iso and infra modules to include the new version so orchestrator instances can be launched from the
  management orchestrator.

[wouterdb]

Hey team! Please add your planning poker estimate with ZenHub @sanderr @arnaudsjs @FloLey @bartv