chore: pull in dependabot updates

[lalitadithya]

Summary

Type of Change

• 🐛 Bug fix
• ✨ New feature
• 💥 Breaking change
• 📚 Documentation
• 🔧 Refactoring
• 🔨 Build/CI

Component(s) Affected

• Core Services
• Documentation/CI
• Fault Management
• Health Monitors
• Janitor
• Other: ____________

Testing

• Tests pass locally
• Manual testing completed
• No breaking changes (or documented)

Checklist

• Self-review completed
• Documentation updated (if needed)
• Ready for review

Summary by CodeRabbit

• Chores
  • Updated dependencies across system components to latest stable versions, including database drivers and core libraries. These updates provide stability improvements, bug fixes, and performance enhancements.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates Go module dependencies across 9 modules, primarily bumping github.com/lib/pq from v1.10.9 to v1.11.1 and other utility libraries to newer versions, with removal of unused indirect dependencies in some modules.

Changes

Cohort / File(s)	Summary
lib/pq version bump (v1.10.9 → v1.11.1) event-exporter/go.mod, fault-remediation/go.mod, health-events-analyzer/go.mod, node-drainer/go.mod, store-client/go.mod	Indirect dependency update applied uniformly across five modules.
lib/pq and google/cel-go updates fault-quarantine/go.mod, platform-connectors/go.mod	lib/pq v1.10.9 → v1.11.1 (indirect); google/cel-go v0.26.1 → v0.27.0. Removes indirect dependency on stoewer/go-strcase v1.3.1 in both modules.
Google API and protobuf updates health-monitors/csp-health-monitor/go.mod	Updates google.golang.org/api v0.262.0 → v0.264.0; updates google.golang.org/genproto/googleapis/rpc to latest timestamp; lib/pq v1.10.9 → v1.11.1 (indirect).
Systemd library update health-monitors/syslog-health-monitor/go.mod	Updates github.com/coreos/go-systemd/v22 from v22.6.0 to v22.7.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 Dependencies dance, versions leap and bound,
lib/pq hops from nine to one-one,
google/cel-go springs up with cheer,
Systemd rolls forward without fear,
All the modules march in synchronized rounds! 🌿

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title 'chore: pull in dependabot updates' directly and accurately summarizes the main change—updating Go dependencies via Dependabot across multiple modules.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ladithyav-dependabot-05-02

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.5.0)

level=error msg="[linters_context] typechecking error: pattern ./...: directory prefix . does not contain main module or its selected dependencies"

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[lalitadithya]

/ok to test 1e42e04

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@platform-connectors/go.mod`:
- Line 9: The upgrade to github.com/google/cel-go v0.27.0 means CEL type
identifiers no longer act as variables; scan all CEL expressions and policy
files in platform-connectors and fault-quarantine for any occurrences where a
type name is being used as a variable (search CEL/policy/rule files and any code
building expressions), and update them to use distinct variable names or
explicitly reference the type (or fully-qualified type access) instead; ensure
functions that construct or evaluate CEL expressions (e.g., any policy
evaluation helpers or expression-builder utilities) no longer assume
type-as-variable behavior and rename shadowing variables or refactor the
expression to avoid relying on the old semantics.