Remove obsolete jq filter test after feature removal

[Copilot]

PR #14887 removed jq filter support from MCP server tools. The status_invalid_jq_filter test case remained, expecting validation errors for malformed jq expressions. Since the jq parameter is now rejected at the schema level as an unexpected property, the test fails.

Changes

• Removed test case: TestMCPServer_ErrorCodes_InvalidParams/status_invalid_jq_filter from pkg/cli/mcp_server_error_codes_test.go
• Cleaned imports: Removed unused testutil package import

The test was validating error messages for invalid jq syntax:

params := &mcp.CallToolParams{
    Name: "status",
    Arguments: map[string]any{
        "jq": ".invalid[syntax",  // No longer accepted
    },
}

Now the parameter itself is rejected before reaching any jq-specific validation logic.

Original prompt

Reference: https://github.com/github/gh-aw/actions/runs/21894085314/job/63206261538#step:10:1

Fix test

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

Removes an obsolete MCP server integration test that still exercised the deprecated jq argument, which is now rejected at the schema/parameter-validation layer after PR #14887 removed jq support.

Changes:

• Removed the status_invalid_jq_filter subtest from TestMCPServer_ErrorCodes_InvalidParams.
• Cleaned up imports by dropping the now-unused pkg/testutil import.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.