Add componentChecks tool, listing checks in rubric

[wesleyjellis]

componentChecks lists the rubric of checks for a given component

Problem

There's no way to view the rubric/check results for a given component

Solution

List the checks and results arranged in the rubric

Checklist

• I have run this code, and it appears to resolve the stated issue.
• This PR has no user interface changes or has already received approval from product management to change the interface.
• Make a changie entry that explains the customer facing outcome of this change.

[Copilot]

Pull Request Overview

This PR introduces the "componentChecks" tool, which lists rubric-based check results for a given OpsLevel component.

• Adds a new tool "componentChecks" in the CLI command with processing logic to format and return check results.
• Updates dependency management in go.mod for the iso8601 package and syncs the submodule pointer for opslevel-go.
• Adds a changelog entry for the new componentChecks tool.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
src/submodules/opslevel-go	Updated subproject commit pointer
src/go.mod	Added direct dependency for github.com/relvacode/iso8601 and removed its indirect listing
src/cmd/root.go	Introduced new types and added the componentChecks tool to the CLI
.changes/unreleased/Added-20250609-161700.yaml	Changelog entry detailing the addition of the componentChecks tool

[rocktavious]

2 suggestions and 1 question

[wesleyjellis]

@rocktavious any idea why the tests are failing to check out the right commit for the submodule? You can see here it grabs the correct SHA but a few lines later it's gone back 1 commit

[rocktavious]

@wesleyjellis its not using the submodule because this line is commented out. https://github.com/OpsLevel/opslevel-mcp/blob/main/src/go.mod#L58

[wesleyjellis]

@rocktavious do we need to cut a release for opslevel-go or should I pin a specific commit with the submodule and uncomment that line?

[rocktavious]

For WIP releases we usually uncomment and commit updates to the submodule. Then part of the release process is to do 1 last commit that updates opslevel-go (when its released) and comment out (something we should probably automate).