feat: detect kapi.yaml recipe (kapi 1.2) alongside legacy *.kapi

[asgeirf]

kapi 1.2 renames the project recipe from a directory-named <name>.kapi to the fixed basename kapi.yaml (discovery now matches kapi.yaml exactly). This makes the TM-cache project detection recognize the new fixed name and the legacy *.kapi glob — transitional and non-breaking for existing users.

Changes

• action.yml — the detect-project step now matches both names.
• action.yml / README.md — cache-tm and project-dir descriptions and the "Restore project TM cache" step note now say "a kapi.yaml recipe (or legacy *.kapi)".

⚠️ Deviation from the suggested one-liner (please review)

The suggested change was a single ls with two operands:

if ls "${PROJECT_DIR}"/kapi.yaml "${PROJECT_DIR}"/*.kapi >/dev/null 2>&1; then

That does not achieve the intended "detect either name". ls exits non-zero if any operand is missing, so with bash it returns:

dir contents	ls a b	intended
only kapi.yaml	false	true
only *.kapi	false	true
both	true	true
neither	false	false

i.e. it would only fire when both a kapi.yaml and a legacy *.kapi exist — breaking the new default case and existing users. I implemented the OR form instead, which yields the intended true/true/true/false:

if ls "${PROJECT_DIR}"/kapi.yaml >/dev/null 2>&1 || ls "${PROJECT_DIR}"/*.kapi >/dev/null 2>&1; then

(Verified empirically under bash for all four cases.)

Untouched

.kapi/ state-dir references are left as-is.

⚠️ Pin set to 1.2.0 — adjust to the actual kapi.yaml-aware release version once cut (kapi.yaml is not yet in a released build). (No version pin exists in this repo; noted for consistency across the kapi 1.2 rename PRs.)