fix(crd): move subresources.status to correct level in teams.hiclaw.io CRD

[googs1025]

Problem

teams.hiclaw.io.yaml has status: {} placed at the wrong indentation level — inside schema.openAPIV3Schema instead of under subresources.

# Before (broken)
      schema:
        openAPIV3Schema:
          ...
        status: {}        # ← wrong: this is an unknown field inside schema
      additionalPrinterColumns:

This causes kubectl apply to fail with:

error: strict decoding error: unknown field "spec.versions[0].schema.status"

Fix

Move subresources.status: {} to the correct level, sibling of schema:

# After (correct)
      schema:
        openAPIV3Schema:
          ...
      subresources:
        status: {}        # ← correct: enables status subresource
      additionalPrinterColumns:

Impact

Anyone running kubectl apply -f hiclaw-controller/config/crd/ against a real K8s cluster (e.g. minikube, kind, or any standard cluster) gets a hard error and the Team CRD fails to register. The embedded mode is unaffected since it uses the CRD files internally via the apiserver subprocess.