Add system_relationship to opslevel_component_type#14723)

[saditya370]

Summary

• Mirror the existing owner_relationship implementation to add system_relationship on the opslevel_component_type resource and datasources
• Bump opslevel-go dependency to v2026.4.13 (OpsLevel/opslevel-go#610) which exposes SystemRelationship on ComponentType and ComponentTypeInput
• Customer request: Springer Nature (account 1174, issue #14687)

Changes

• Resource: added system_relationship attribute with management_rules nested block (Create/Update/Read)
• Datasources: added system_relationship to both opslevel_component_type and opslevel_component_types datasources
• Tests: added field accessibility assertions and a dedicated resource_component_type_system_relationship test case
• Docs: regenerated via task docs — additive sections for system_relationship on all 3 doc pages

Notes

• system_relationship is structurally identical to owner_relationship (single management_rules field, same ManagementRuleInput element type) — confirmed against the backend Ruby source
• componentTypePropagateSystemRelationship is intentionally out of scope — it's a one-shot bulk operation that doesn't map to declarative Terraform, and there's no precedent for it with owner_relationship

Test plan

• go build ./... — passes
• task test — 104 passed, 0 failed
• Schema introspection against local backend confirms systemRelationship on both ComponentType and ComponentTypeInput
• End-to-end componentTypeCreate mutation with systemRelationship round-trips correctly
• task apply with a real system_relationship config against a sandbox account (manual verification)

Dependency

• Requires OpsLevel/opslevel-go#610 — merged, released as v2026.4.13

[andrewstillv15]

I think that the MR title is incorrect.

[saditya370]

I think that the MR title is incorrect.

Thanks , fixed