v1.1.1 — fix: named connections were dropped in the packaged 1.1.0

Hotfix for 1.1.0. The 1.1.0 packaged `@sqlanvil/core` silently dropped the `connections` map from `workflow_settings.yaml` when run through the CLI, so connection-tagged declarations failed with Unknown connection "…". The bug was a protobuf-map + minification interaction ({...projectConfig} spread dropped map fields once the core bundle was minified); it wasn't caught because the unit tests run the unminified library, never the packaged bundle. Fixed by setting connections explicitly in the projectConfig merge (as vars already was).

If you're using the named connections / connection: on declarations feature from 1.1.0, upgrade to 1.1.1.

npm install -g @sqlanvil/cli   # 1.1.1

Verified end-to-end: the supabase_bigquery_mailing_list example (now refactored to the named-connections model) compiles cleanly through the packaged bundle.