CLI migration fails if database does not support SSL

[bryanoltman]

If a psql database requires ssl, CLI-triggered migration will fail.

Steps to reproduce

Following the README instructions:

1. Create a new project
2. Define a Model class
3. Create a containerized database using the following:

docker pull postgres
docker run \               
    --name stormberry_demo \
    -p 127.0.0.1:5432:5432 \
    -e POSTGRES_USER=postgres \
    -e POSTGRES_DB=stormberry_demo \
    -e POSTGRES_PASSWORD=password \
    -d \
    postgres

4. Run dart run stormberry migrate
5. See:

Select a database to update: stormberry_demo
Enter the database host address: 127.0.0.1
Enter the database port: 5432
Enter the database username: postgress
Enter the database password: 
Severity.error Server does not support SSL, but it was required (default configuration). To disable secure connections, use `ConnectionSettings(sslMode: SslMode.disable)`.
#0      PgConnectionImplementation._connect (package:postgres/src/v3/connection.dart:372:9)
<asynchronous suspension>
#1      PgConnectionImplementation.connect (package:postgres/src/v3/connection.dart:238:29)
<asynchronous suspension>
#2      _DatabaseWithOneConnection._tryOpen (package:stormberry/src/core/database.dart:138:24)
<asynchronous suspension>
#3      MigrateCommand.run (package:stormberry/src/cli/runner.dart:135:5)
<asynchronous suspension>
#4      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#5      main (file:///Users/bryanoltman/.pub-cache/hosted/pub.dev/stormberry-0.18.0/bin/stormberry.dart:12:5)
<asynchronous suspension>

[schultek]

Run with migrate --no-ssl

[bryanoltman]

Makes sense. It'd probably be good to add special handling for this error to make sure the user knows that the --no-ssl flag exists?