Flowable Task UI cannot be operated on root web application context

**Describe the bug**
The Flowable Task UI works well if a non root web context like '/flowable-task' is used.
But if the application is operated on the root web context ('/'), then navigation to the 'Task App' fails. Only an empty page with an empty header will be shown.

**Expected behavior**
The Application should work independently of the chosen web context.

**Code**
Seems to me the issue is caused by the following code part in app-cfg.js:
`var pathname = window.location.pathname.replace(/^(\/[^\/]*)(\/.*)?$/, '$1').replace(/\/$/, '');`

Operated on a '/flowable-task' web context the value of pathname will always be '/flowable-task'.
Operated on a '/' web context the value of pathname will be "" on the main page and '/workflow' as soon a navigated to the "Task App" (or any other deployed app). This breaks all further backend calls.

**Additional context**
Tested with the master code of the Flowable Task UI but also applies to the current release version (and probably older versions).