Hotfix: bump version-code floor past the 669 burned by the expired 1.6.2 edit

[troymyree-lang]

Summary

• get-next-version-code.sh only checks versionCodes committed to a Play track, so it can't see one burned by an upload to an edit that later expired uncommitted -- exactly what happened during today's 1.6.2 release attempt (versionCode 669 burned, then rejected on retry)
• Adds a one-off floor above 669 to unblock 1.6.2 right now
• Durable fix (a persisted ratchet that accounts for attempted-but-uncommitted uploads) tracked separately in get-next-version-code.sh can collide with versionCodes burned by a failed/expired Play edit #700

Ticket

Part of #700

Type of Change

• Bug fix
• CI/CD

Testing

• Manual testing performed

Verified with bash -n (syntax) and by manually tracing the jq/arithmetic logic against both the pre- and post-collision states. Real verification is the next tag-triggered release run actually succeeding.

Checklist

• Tests pass locally (./gradlew testDebug)
• No API keys or secrets in code
• CLAUDE.md updated (if new pattern introduced) -- not needed, this is a one-off floor with the durable fix tracked in get-next-version-code.sh can collide with versionCodes burned by a failed/expired Play edit #700