Add ability to add uri args to secret templates

[halkeye]

scenario: Wanting to create a secret that has logging enable uri, but don't want to hard code connection uris in the template string

So something like

DB_LOGGING_URL: postgresql://{{.Role}}:{{.Password}}@{{.Host}}/{{.Database}}?{{ "logging=true" | mergeUriArgs }}

[halkeye]

did you just merge/rebase? or did you change something I missed?

[pcallewaert]

I only did a rebase, the PR looks good on first sight, but I need to free some time to review it properly

[Copilot]

Pull Request Overview

This PR adds the ability to dynamically add URI arguments to secret templates without hardcoding connection URIs in the template strings. It introduces a new mergeUriArgs template function that allows merging URI arguments from both the template and the Postgres configuration.

• Added UriArgs field to the TemplateContext struct and corresponding pgUriArgs field to the controller
• Implemented a mergeUriArgs template function that merges URI query parameters
• Added comprehensive test coverage for the new functionality with various merge scenarios

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
pkg/utils/template.go	Implements the mergeUriArgs template function and adds UriArgs to the template context
internal/controller/postgresuser_controller.go	Integrates URI args configuration into the controller and adds URI_ARGS to generated secrets
internal/controller/postgresuser_controller_test.go	Adds comprehensive test cases for the new URI args merging functionality
README.md	Documents the new URI_ARGS secret field and mergeUriArgs template function

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[pcallewaert]

Looks good, thank you!