🐛 Fix wrong go-style UUID regexp - made portal links fail

[mrnicegyu11]

What do these changes do?

Portal links opening failed in master.
The reason is that the Traefik-Rule for sending /study/UUID to the webserver would not trigger, as the old-style go-regexp doesnt work anymore in traefik-v3. I have changed the old UUID-catching Regexps to the style of the already updated, already functional one that catches modern (dv2) dynamic services.

I will forcemerge this after some consideration.

Related issue/s

How to test

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

[sonarqubecloud]

Please retry analysis of this Pull-Request directly on SonarCloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.1%. Comparing base (cafbf96) to head (4a0de8b).
Report is 480 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #6268      +/-   ##
=========================================
+ Coverage    84.5%   88.1%    +3.5%     
=========================================
  Files          10    1471    +1461     
  Lines         214   61011   +60797     
  Branches       25    2063    +2038     
=========================================
+ Hits          181   53783   +53602     
- Misses         23    6915    +6892     
- Partials       10     313     +303     

Flag	Coverage Δ
integrationtests	64.8% <ø> (?)
unittests	86.1% <ø> (+1.5%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1421 files with indirect coverage changes

[pcrespov]

@mrnicegyu11 I propose to create a test in tests/environment-setup/test_traefik_setup.py that checks the regex against some known entrypoints

This is an idea of it ...

import pytest
import re
import yaml

# Function to load the docker-compose file and extract the regex
def extract_regex_from_docker_compose(file_path):
    with open(file_path, 'r') as file:
        compose_data = yaml.safe_load(file)
        labels = compose_data['services']['traefik']['labels']
        for label in labels:
            if 'traefik.http.routers' in label and 'PathRegexp' in label:
                # Extract the regex from the label
                regex = re.search(r'PathRegexp\(`(.*)`\)', label).group(1)
                return regex
    return None

# Test cases with parametrized paths
@pytest.mark.parametrize("path,expected", [
    ("/x/12345678-1234-1234-1234-123456789abc", True),  # Valid UUID
    ("/x/abcdef12-3456-7890-abcd-ef1234567890", True),  # Valid UUID
    ("/x/invalid-uuid-1234-1234-1234-123456789abc", False),  # Invalid UUID
    ("/y/12345678-1234-1234-1234-123456789abc", False),  # Valid UUID but wrong path
    ("/x/1234-5678-1234-1234-123456789abc", False),  # Invalid UUID format
])
def test_traefik_path_regex_matching(path: str, expected: bool):
    # Load the regex from the docker-compose file
    regex = extract_regex_from_docker_compose('docker-compose.yml')
    
    # Compile the regex with the appropriate flags (case insensitive)
    compiled_regex = re.compile(regex, re.IGNORECASE)
    
    # Test if the path matches the regex
    match = compiled_regex.match(path)
    assert (match is not None) == expected

[pcrespov]

Same story here. We need a way to reliably enforce certain conditions and avoid errors