Add NoResetOnClose=true to PostgreSQL connection strings missing it

[LoopedBard3]

Commit 36ab8b9 removed Multiplexing=true and tightened Program.cs to require NoResetOnClose=true, but missed adding it to connection strings that previously relied on Multiplexing=true to pass the check.

Fixes Fortunes, Fortunes EF, and Fortune Dapper failures in the benchmarks-ci-01 Trends Database pipeline.

[Copilot]

Pull request overview

This PR updates PostgreSQL connection strings in benchmark scenario YAMLs to include NoResetOnClose=true, aligning scenario configuration with the stricter Npgsql connection-string validation enforced by src/Benchmarks/Program.cs.

Changes:

• Add NoResetOnClose=true to PostgreSQL connection strings in scenarios/mono.benchmarks.yml.
• Add NoResetOnClose=true to the PostgreSQL connection string used by scenarios/database.benchmarks.yml.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
scenarios/mono.benchmarks.yml	Adds NoResetOnClose=true to multiple PostgreSQL scenario connection strings to satisfy runtime validation.
scenarios/database.benchmarks.yml	Adds NoResetOnClose=true to the PostgreSQL job connection string to prevent startup validation failures.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.