Fix komodoenv bleeding tracking

[andreas-el]

Issue
Resolves https://github.com/equinor/komodo-releases/issues/7334

This branch is testable onprem, and produce a komodoenv that can be updated.
It's not a perfect test though.

(mystable + 2025.04.05-py311-rhel8) [andrli@st-lintgx0275 komodoenv]$ komodoenv --root /prog/res/komodo --track bleeding test-me-now2
Info: If you encounter issues with the Jupyter environment or the 'rips' package, try running 'komodoenv-update' or sourcing the komodoenv again.

Warning: Tracking a bleeding release of komodo. It changes every day. You will need to recreate komodoenv in order to use new executables in komodo.

        venv    using /private/andrli/project/mystable/root/bin/python
      create    komodoenv.conf
      create    /private/andrli/project/komodoenv/test-me-now2/root/lib/python3.11/site-packages/zzz_komodo.pth
      create    root/bin/komodoenv-update
         run    root/bin/komodoenv-update
     install    pip
      remove    root/shims/komodoenv

Komodoenv has successfully been generated. You can now pip-install software.

    $ source /private/andrli/project/komodoenv/test-me-now2/enable

Pre review checklist

• Read through the code changes carefully after finishing work
• Make sure tests pass locally (after every commit!)
• Prepare changes in small commits for more convenient review (optional)
• PR title captures the intent of the changes, and is fitting for release notes.
• Updated documentation
• Ensured that unit tests are added for all new behavior (See
  Ground Rules),
  and changes to existing code have good test coverage.

Pre merge checklist

• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.

[berland]

🕺🏻