Add support for custom connection string parameters in PostgreSQL connection URL

# Summary

Add support for custom connection string parameters in PostgreSQL connection URL for Argo Workflows, specifically to allow setting `binary_parameters=yes`. Currently, the connection string configuration doesn't support adding custom parameters, which causes issues when using PgBouncer with PostgreSQL for archiving and offloading workflows.

## Use Cases

When would you use this?

The modification is particularly important for production environments where PgBouncer is commonly used as a standard practice for PostgreSQL connection pooling and management. Or any other custom use case people may have.

---

**Message from the maintainers**:

Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.

No files, tests, or entry points are named. Start by locating Argo Workflows' PostgreSQL connection URL configuration and the archive/offloading connection setup; determine how custom parameters such as binary_parameters=yes can be passed through. Done means custom PostgreSQL parameters work with PgBouncer without breaking existing connection configuration.

Written by the indexing model from the issue text.