sec-vuln: upgrade dependencies

[himadrisingh]

Fixes

• https://github.com/rilldata/rill/security/dependabot/459
• https://github.com/rilldata/rill/security/dependabot/460
• https://github.com/rilldata/rill/security/dependabot/457
• https://github.com/rilldata/rill/security/dependabot/458
• https://github.com/rilldata/rill/security/dependabot/461

Checklist:

• Covered by tests
• Ran it and it works as intended
• Reviewed the diff before requesting a review
• Checked for unhandled edge cases
• Linked the issues it closes
• Checked if the docs need to be updated. If so, create a separate Linear DOCS issue
• Intend to cherry-pick into the release branch
• I'm proud of this work!

[begelundmuller]

LGTM

[himadrisingh]

Root cause: upgrading docker/compose/v5 to v5.1.2 pulled in gotest.tools/v3@v3.5.2 as a new transitive dependency. That library's init() registers flag.Bool("update", ...). Since dependency init() functions run before the importing package's
variable initializers, gotest.tools registers the flag first, and resolvers_test.go:58's var update = flag.Bool("update", ...) then panics with "flag redefined".

Fix (runtime/resolvers/resolvers_test.go):

• Replaced the package-level var update = flag.Bool(...) with an init() that only registers the flag if flag.Lookup("update") == nil (same pattern gotest.tools itself uses)
• Changed the usage in TestResolvers to look up the flag value via flag.Lookup("update") after flag.Parse() instead of dereferencing a package-level pointer