go.mod: bump gorm.io/driver/postgres to resolve downstream vuln

[ajgajg1134]

What does this PR do?

Closes #1816
Also, switches the driver used to the microsoft forked version of mssql driver since both drivers register themselves in their init (which means if you accidentally import both as we were now doing since it was changed in gorm it made go sql panic).
On top of that gorm introduced a breaking change here: go-gorm/sqlserver#72 so that version also needed to be updated
ALSO. no clue why but maybe due to a new version of gofmt but lots of lint changes 😭

Motivation

Turns out gorm.io/driver/postgres relied on jackc/pgx/v4 which relied on satori/go.uuid which was vulnerable to bad random data.

Describe how to test/QA your changes

The integration tests should be sufficient here

Reviewer's Checklist

• Changed code has unit tests for its functionality.
• If this interacts with the agent in a new way, a system test has been added.

[pr-commenter]

Benchmarks

Comparing candidate commit d162238 in PR branch andrew.glaude/BumpGORM with baseline commit 1b5ba27 in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 18 metrics, 0 unstable metrics.