[V2][Sessions] Do not try to update the database schema each time the application is launched

[LoicPoullain]

Issue

Sessions: when launching the application, Foal makes a request to the database to create the session table if it does not exist.

This has two drawbacks:

• This may make too many undesirable requests to the db in a severless environment.
• The database schema is updated at runtime outside the classical migration process. This practice can be dangerous and it does not allow to keep a traceability of the modifications of the database schema unlike migrations (revert, etc).

Solution

Use migrations to generate the session table. They can be generated automatically from an entity DatabaseSession exported from @foal/typeorm.

[LoicPoullain]

Resolved in v2.