[SOA-704] feat(app): Add Session Pool Options to the Spanner connection

[MuFa117]

Description of change

Typeorm does not offer sessionPool options to be passed through the connection and uses the default ones. We would want to eventually control them from the client, so this would add this opportunity.

Options based on https://github.com/googleapis/nodejs-spanner/blob/main/src/session-pool.ts#L168

Pull-Request Checklist

• Code is up-to-date with the master branch
• npm run format to apply prettier formatting
• npm run test passes with this change
• This pull request links relevant issues as Fixes #0000
• There are new or updated unit tests validating the change
• Documentation has been updated to reflect this change
• The new commits follow conventions explained in CONTRIBUTING.md

[javierdelafuentesales]

Looks good, were you able to test it?

[MuFa117]

Looks good, were you able to test it?

I tested it locally and all was good :) (I updated the built code within node_modules)

[Xevi]

Shall we test it on staging-eu with real application? Before we merge this one??

[javierdelafuentesales]

Shall we test it on staging-eu with real application? Before we merge this one??

@Xevi How do you test it on staging-eu without merging it? I think that first we need to get the new version.

[MuFa117]

@Xevi merging this PR would still be fine until we bump up client’s version, so beta/prod is going to be fine, but I’m gonna bump the version on onair-api and deploy to staging-eu for sure if that’s what you were talking about

[Xevi]

We could always modify the action to make this branch to be able to get built. But should be fine if we are not using this version to anything in prod