Ci fails on frontend tests

[Dassderdie]

> digital-fuesim-manv-frontend@0.0.0 test
> jest --runInBand --coverage --verbose

PASS Frontend src/app/core/optimistic-action-handler.spec.ts
  OptimisticActionHandler
    ✓ should correctly apply not optimistic proposed actions when response is true (5 ms)
    ✓ should correctly apply not optimistic proposed actions when response is false (2 ms)
    ✓ should correctly perform actions (1 ms)
    ✓ should correctly apply optimistic actions (2 ms)
    ✓ should keep the right order when applying optimistic updates and performed updates (1 ms)
    ✓ should perform already proposed actions after the optimistic update is done (*** ms)

------------------------------|---------|----------|---------|---------|-------------------
File                          | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
------------------------------|---------|----------|---------|---------|-------------------
All files                     |     100 |      100 |     100 |     100 |                   
 optimistic-action-handler.ts |     100 |      100 |     100 |     100 |                   
------------------------------|---------|----------|---------|---------|-------------------

=============================== Coverage summary ===============================
Statements   : 100% ( ***/*** )
Branches     : 100% ( 4/4 )
Functions    : 100% ( 5/5 )
Lines        : 100% ( ***1/***1 )
================================================================================
Test Suites: 1 passed, 1 total
Tests:       6 passed, 6 total
Snapshots:   0 total
Time:        4.71*** s
Ran all test suites.
node:internal/event_target:777
  process.nextTick(() => { throw err; });
                           ^

Error: Unknown worker message type message
This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues

    at new NodeError (node:internal/errors:***71:5)
    at Function.fail (node:internal/assert:20:9)
    at Worker.[kOnMessage] (node:internal/worker:***17:12)
    at MessagePort.<anonymous> (node:internal/worker:201:57)
    at ZoneDelegate.Object.<anonymous>.ZoneDelegate.invokeTask (/home/runner/work/digital-fuesim-manv/digital-fuesim-manv/frontend/node_modules/zone.js/bundles/zone-testing-bundle.umd.js:441:***5)
    at Zone.Object.<anonymous>.Zone.runTask (/home/runner/work/digital-fuesim-manv/digital-fuesim-manv/frontend/node_modules/zone.js/bundles/zone-testing-bundle.umd.js:212:51)
    at ZoneTask.Object.<anonymous>.ZoneTask.invokeTask [as invoke] (/home/runner/work/digital-fuesim-manv/digital-fuesim-manv/frontend/node_modules/zone.js/bundles/zone-testing-bundle.umd.js:52***:***8)
    at invokeTask (/home/runner/work/digital-fuesim-manv/digital-fuesim-manv/frontend/node_modules/zone.js/bundles/zone-testing-bundle.umd.js:166***:18)
    at MessagePort.globalZoneAwareCallback (/home/runner/work/digital-fuesim-manv/digital-fuesim-manv/frontend/node_modules/zone.js/bundles/zone-testing-bundle.umd.js:1689:21)
    at MessagePort.[nodejs.internal.kHybridDispatch] (node:internal/event_target:562:20) {
  code: 'ERR_INTERNAL_ASSERTION'
}

[Dassderdie]

The MessagePort stuff seems to come from Node workers. Maybe we could try to limit jest in the frontend to one worker via https://jestjs.io/docs/cli#--maxworkersnumstring

[Dassderdie]

Currently fixed via --forceExit