mock postgres database v1 in more tests [SW-403]

[PooyaRaki]

Summary

Added PostgresDatabaseModule mock to additional unit tests to enhance test coverage and reliability.
When registering Notification V2, we encountered a "too many connections" error. To address this, we need to mock Database V1 and V2 in all tests. This PR adds the missing mocks.

Changes

• Updated existing unit tests to utilize the mock for improved isolation and consistency.
• Verified that tests maintain expected behavior with the mock implementation.

How to test/reproduce

• Check out branch Notification migration #2063.
• Run the unit tests.
• You should encounter the "too many connections" error.

[hectorgomezv]

Check out branch https://github.com/safe-global/safe-client-gateway/pull/2063.
Run the unit tests.
You should encounter the "too many connections" error.

I think the error there is related to a non-graceful app shutdown during the test execution, so maybe the database connections are not properly closed in your local setup. You can check the error in the CI there is

TypeError: Configuration key "jwt.issuer" does not exist

If the dependency graph is modified on purpose (and the auth-related modules are needed at startup), then you need to include placeholders for JWT_ISSUER and JWT_SECRET.

[PooyaRaki]

Check out branch https://github.com/safe-global/safe-client-gateway/pull/2063.
Run the unit tests.
You should encounter the "too many connections" error.

I think the error there is related to a non-graceful app shutdown during the test execution, so maybe the database connections are not properly closed in your local setup. You can check the error in the CI there is

TypeError: Configuration key "jwt.issuer" does not exist

If the dependency graph is modified on purpose (and the auth-related modules are needed at startup), then you need to include placeholders for JWT_ISSUER and JWT_SECRET.

I believe that’s a different issue. This PR addresses a problem with the unit tests, whereas the issue you’re seeing in the PR is related to the e2e tests. You need to run unit tests and monitor your database connections as well to face the issue this PR fixes.

[hectorgomezv]

I believe that’s a different issue. This PR addresses a problem with the unit tests, whereas the issue you’re seeing in the PR is related to the e2e tests. You need to run unit tests and monitor your database connections as well to face the issue this PR fixes.

The issue in the other branch is related to the unit tests, not e2e, as you can see in the screenshot.

But I'm fine with the changes in the PR 👍 Thanks for looking into this @PooyaRaki !

[PooyaRaki]

I believe that’s a different issue. This PR addresses a problem with the unit tests, whereas the issue you’re seeing in the PR is related to the e2e tests. You need to run unit tests and monitor your database connections as well to face the issue this PR fixes.

The issue in the other branch is related to the unit tests, not e2e, as you can see in the screenshot.

But I'm fine with the changes in the PR 👍 Thanks for looking into this @PooyaRaki !

Initially, it was also the e2e tests that were affected. Please take a look:
https://github.com/safe-global/safe-client-gateway/actions/runs/11542383150