fix: prevent invoking destroyed injector

[dhhyi]

PR Type

[x] Bugfix

What Is the Current Behavior?

While doing performance tests, the SSR deployments regularly crash with the following stacktrace:

1 b2c /dist/b2c/server/webpack:/node_modules/@angular/core/fesm2020/core.mjs:7970
            throw new RuntimeError(205 /* RuntimeErrorCode.INJECTOR_ALREADY_DESTROYED */, ngDevMode && 'Injector has already been destroyed.');
                  ^
1 b2c Error: NG0205
    at R3Injector.assertNotDestroyed (/dist/b2c/server/webpack:/node_modules/@angular/core/fesm2020/core.mjs:7970:19)
    at R3Injector.get (/dist/b2c/server/webpack:/node_modules/@angular/core/fesm2020/core.mjs:7877:14)
    at Object.next (/dist/b2c/server/webpack:/src/app/core/utils/module-loader/module-loader.service.ts:23:36)
    at ConsumerObserver2.next (/dist/b2c/server/webpack:/node_modules/rxjs/dist/cjs/internal/Subscriber.js:113:33)
    at SafeSubscriber2._next (/dist/b2c/server/webpack:/node_modules/rxjs/dist/cjs/internal/Subscriber.js:80:26)
    at SafeSubscriber2.next (/dist/b2c/server/webpack:/node_modules/rxjs/dist/cjs/internal/Subscriber.js:51:18)
    at onNext (/dist/b2c/server/webpack:/node_modules/rxjs/dist/cjs/internal/operators/filter.js:9:164)
    at OperatorSubscriber2._next (/dist/b2c/server/webpack:/node_modules/rxjs/dist/cjs/internal/operators/OperatorSubscriber.js:33:21)
    at OperatorSubscriber2.next (/dist/b2c/server/webpack:/node_modules/rxjs/dist/cjs/internal/Subscriber.js:51:18)
    at /dist/b2c/server/webpack:/node_modules/rxjs/dist/cjs/internal/operators/distinctUntilChanged.js:18:28

What Is the New Behavior?

Subscription in module loader is stopped.

Does this PR Introduce a Breaking Change?

[ ] Yes
[ ] No

Other Information

AB#89238

[SGrueber]

@dhhyi Would it be recommended to stop open subscriptions in other services, too if they are destroyed ?

[dhhyi]

@dhhyi Would it be recommended to stop open subscriptions in other services, too if they are destroyed ?

Only this particular case caused some issues that showed in the error log. I wouldn't make it a rule as services are usually only destroyed at the end of life of the application.