ci: fix resource workflow path filters

[Jeremy1844]

Root cause

GitHub Actions paths filters are repository-rooted, but the asset deployment workflow names both workflow files with a leading ./. Those patterns are invalid and cannot match the intended workflow-file changes.

Change

Remove the leading relative segment from the two workflow-file filters and add a regression test that requires both repository-rooted paths and rejects .//../ path filters.

Evidence

• Base: 9d237dd4fb37dd1fb936e3f9649020cc43a374c8 (stage)
• Regression commit: d1edf40631fdd031aabd6b145bc7fb74ed448150 — 0/3 introduced tests passed
• Fix commit: 8b45531bff39f54842c6d88faba1bcc3dcfc0be8 — 3/3 passed
• Actionlint 1.7.12 reports both invalid glob paths on red and neither on the fixed head; the head retains only the pre-existing actions/setup-node@v3 runtime finding, which is a separate root
• Refreshed red/fix patch IDs exactly match the previously reproduced patches
• src, assets, package.json, and yarn.lock Git objects are identical to the base
• Strict object-connectivity and diff checks passed

Scope and rollout

This PR changes two path-filter lines and one test only. It has zero path or semantic overlap with #76 and contains no content, asset, dependency, schema, persistence, credential, permission, action-version, or deployment logic change.

Before merge, approve a non-production hosted pull-request check that proves edits to each named workflow select this workflow without using deployment credentials. Rollback is a revert of this two-commit range; an immutable deployed artifact is unaffected because this changes trigger selection only.