Setting baseHref in MULTI_CHANNEL configuration so that it contains multiple slashes fails

[gorpet]

PWA 6.0.0
ICM 7.10.41.9-LTS B2X

Actual Behavior

When setting baseHref property in MULTI_CHANNEL environment variable to contain multiple slashes (e.g. /za/en), PWA stops working and gives 404 errors with url "baseHref"/home.

Expected Behavior

When setting baseHref property in MULTI_CHANNEL environment variable to contain multiple slashes (e.g. /za/en), PWA works as expected and correct channel homepage is displayed with url "baseHref"/home.

Steps to Reproduce the Bug

Steps to reproduce the behavior:

1. Set MULTI_CHANNEL environment variable to:

MULTI_CHANNEL: |
      .+:
        - baseHref: /za/en
          lang: en_ZA
          channel: HSA-Site
        - baseHref: /pt/pt
          lang: pt_PT
          channel: HPT-Site

2. Build nginx docker image and start it
3. Start PWA app
4. Try to open home page with http://localhost:4199/za/en/home
5. Error is shown and in console multiple js files are tried to be fetched from /za/xxxxx.js (/za/1936.js) and it should be /xxxxx.js

Additional Context, like Screenshots, Log File Snippets etc.

AB#106380