[RND-513] Jest is taking too long

[andonyns]

This is an initial research about improving Jest performance.

Results:

1. Fix error messages logged when running tests. See this run as an example.

• This meant that some tests were trying to connect to a real database which lead to a timeout. This did not affect the actual test but the setup.
• Some mocks that were not returning a value were causing the tests to call the real implementation.

2. Add missing mocked environment variables.

• This made a test fail because it was also attempting to do a DB connection.

3. Add tsconfig file for tests to attempt to simplify compilation.

ℹ Note
The unit tests are still very slow, so it is important to continue to review tests individually (seeing the logged execution time) since it can be a signal that the tests are doing things that should be mocked.
ts-jest compilation tends to be slow but there are indications that some tests are taking too long to be this the issue. The attached thread suggests using swc but there are still some issues with jest mocks in this library, although it might be interesting to come back to this in the future to explore more about the tool.