feat(workflow): add SDK parity dispatch workflow

[salihdev0]

• Introduced a new GitHub Actions workflow for SDK parity dispatch.
• Triggers on push and pull request events for specific paths.
• Utilizes a reusable workflow from tapsilat/tapsilat-sdk-parity.

[Copilot]

Pull request overview

Adds a new GitHub Actions workflow to dispatch SDK parity checks via a reusable workflow in tapsilat/tapsilat-sdk-parity, scoped to changes in Zig build files and src/.

Changes:

• Introduces sdk-parity-dispatch.yml workflow triggered on push, pull_request, and workflow_dispatch.
• Limits automatic triggers to changes under src/**, build.zig, and build.zig.zon.
• Calls a reusable workflow and inherits secrets from the caller.

---

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

[Copilot]

The reusable workflow is referenced with @main. This is mutable and can change behavior (and potentially expand the impact of secrets: inherit) without any change in this repo. Prefer pinning to an immutable ref (a version tag or commit SHA) so dispatch behavior is reproducible and supply-chain risk is reduced.

[Copilot]

push is configured without a branches filter, so this workflow will run on pushes to any branch (and path filters are not evaluated for tag pushes). If the intent is to only dispatch parity checks for the default branch (as in .github/workflows/test.yml), add an explicit branches: [main] (and/or tags-ignore) to avoid unexpected dispatches.

[Copilot]

Because this workflow calls into a reusable workflow and inherits secrets, consider explicitly setting least-privilege permissions: for the workflow/job (rather than relying on repo/org defaults). This helps prevent accidental privilege expansion if defaults change.