refactor(capability-matrix): remove transitional sdk-ref shim from compliance actions

[spydon]

What

Removes the transitional sdk-ref input and its gated self-checkout steps from the sdk-compliance-validate and sdk-compliance-check-setup composite actions.

Why

The shim existed for pre-v1.4.0 reusable workflows, which referenced these actions remotely at @main and passed a non-empty sdk-ref so the actions could perform their own checkouts. All consumers of those workflows have now merged their bumps to v1.5.0 (supabase-flutter#1782, supabase-js#2637, supabase-py#1596, supabase-swift#1300), and since #112 the old .github/actions/ paths no longer exist on main anyway, so nothing can reach these actions with a non-empty sdk-ref anymore:

• Current reusable workflows check out _sdk-spec themselves at inputs.sdk-ref || job.workflow_sha and reference the actions locally without passing sdk-ref.
• supabase-go is pinned to the v1.3.0 go workflow, which references the actions at the frozen v1.2.0 SHA, so it never executes the action code on main. Its bump (including dropping the sdk-ref: main override) is tracked separately.

The sdk-ref input on the reusable workflows themselves is intentionally kept: supabase-go still passes it, and it remains the documented pre-merge testing override.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 55866e3c-70b6-4760-b0db-2fd96edb215e

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}