PC-18992: Add multi-query support for Sumo Logic metrics

[nikodemrafalski]

Summary

Add multi-query (ABC pattern) support for Sumo Logic metrics integration, aligning the Terraform provider with the updated nobl9-go SDK.

Changes

Sumo Logic Multi-Query Support

• Added queries block to the sumologic schema, enabling multiple named queries (rows A–F) that can reference each other
• Deprecated the singular query attribute in favor of the new queries block
• Added schema validation ensuring query and queries are mutually exclusive
• Added plan drift handling for the new queries attribute

ThousandEyes Fix

• Added account_group_id attribute to the thousandeyes schema to match the updated SDK

Other

• Bumped nobl9-go and other dependencies
• Updated documentation with Sumo Logic multi-query examples
• Added unit and acceptance test coverage

Example Usage

query {
  sumologic {
    type        = "metrics"
    quantization = "15s"
    rollup      = "Avg"
    queries {
      row_id = "A"
      query  = "metric=cpu_idle"
    }
    queries {
      row_id = "B"
      query  = "#A + 1"
    }
  }
}

Test Plan

• Unit tests pass (make test/unit)
• Acceptance tests pass against dev-demo-3.nobl9.dev (all 160+ SLO subtests)

Part of PC-18992.

[skrolikiewicz]

Review Summary

Overall well-structured PR that follows existing codebase conventions. Some positive highlights:

• Plan drift handling is well implemented — types.StringNull() on Query when Queries is populated prevents perpetual drift
• Bidirectional ConflictsWith validators are correctly set up on both query and queries
• Custom sumoLogicQueriesTypeValidator cleanly prevents queries for logs type
• Template rendering fix (all slice elements instead of just first) is safe — existing tests use single-element slices so no breakage
• Model type change (string → types.String) is correct and doesn't require a schema version bump
• ThousandEyes account_group_id addition follows established codebase patterns

Left a few suggestions inline — nothing blocking, just ideas to harden validation and improve test coverage.

[skrolikiewicz]

ConflictsWith ensures mutual exclusivity, but there's no validation that at least one of query or queries is provided. A user could submit a sumologic block with only type set and get a confusing API-level error. Consider adding stringvalidator.AtLeastOneOf(path.MatchRelative().AtParent().AtName("queries")) here.

[skrolikiewicz]

No validation for duplicate row_id values. A user could define two queries both with row_id = "A". Either add a custom validator checking uniqueness, or confirm the SDK catches this and document that decision.

[skrolikiewicz]

This removal (write-only arguments note + retrieve_historical_data_from type change) appears unrelated to the Sumo Logic multi-query feature. Consider splitting into a separate commit or calling it out in the PR description.

[skrolikiewicz]

Consider adding negative test cases: (1) queries with type = "logs" to verify the custom validator, (2) both query and queries empty, (3) both set simultaneously. These are cheap to add and protect against regressions.

[paulina-n9]

Verified CRUD operations for both Agent and Direct modes that support the ABC pattern.

Additionally, confirmed that unsupported configurations (Agent, Direct, and Logs data types) are handled correctly.