chore(maker): update maker version policy for 0.0.21-beta.3

[taptap-cps-bot]

Updates config/maker-version-policy.json after publishing
@taptap/maker@0.0.21-beta.3 with npm tag
beta.

The workflow only updates latest or latest_beta plus updated_at.
Manual policy fields such as minimum_supported, blacklist, and message
are preserved for review-driven changes.

[greptile-apps]

Greptile Summary

This PR updates the Maker beta version policy after publishing @taptap/maker@0.0.21-beta.3. The main changes are:

• latest_beta now points to 0.0.21-beta.3.
• updated_at was refreshed to the new publish timestamp.
• Manual policy fields remain unchanged.

Confidence Score: 5/5

The change is limited to a version policy metadata update and appears safe to merge.

Only latest_beta and updated_at changed, matching the release-policy update described for @taptap/maker@0.0.21-beta.3; no code paths or manual policy fields were modified.

T-Rex Logs

What T-Rex did

• Observed and logged the pre-change base JSON state to verify the initial values.
• Observed and logged the head JSON state after updates, with latest_beta 0.0.21-beta.3 and updated_at 2026-06-26T08:59:59.373Z.
• Captured a comparison artifact showing the base and head states, confirming that latest, minimum_supported, blacklist, and message are preserved while latest_beta and updated_at change as claimed.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "chore(maker): update maker version polic..." | Re-trigger Greptile}