chore(release): 0.1.24

[CarmenDou]

What

Release 0.1.24. Two changes have been sitting on main since 0.1.23 went out, so the published CLI
does not have them yet.

• 501bdee template upgrade and rollback: insta template upgrade <service> and
  insta template rollback <service>, the CLI half of insta-platform #645, which is on production
• 479bf05 postgres limits says a queued resize is not applied yet, and databases default to
  always-on (IOZI-30)

How

Only the version, the way every release here is cut: package.json and package-lock.json,
0.1.23 to 0.1.24. Merging this does not publish anything. The tag v0.1.24 pushed on main
afterwards runs the release workflow, which builds the binaries and publishes npm.

A workflow_dispatch release is deliberately not used: the workflow's own header says it builds
the GitHub binaries only and publishes package.json's version, so dispatching would ship binaries
at one version and leave npm on the previous one.

Verify

• after merge, push v0.1.24 on main and npm view insta version prints 0.1.24
• insta template upgrade --help then describes the added-service rows it actually prints,
  which 0.1.23 does not have

---

Summary by cubic

Bumps the insta CLI to 0.1.24 so the template upgrade/rollback commands and postgres limits changes that have been on main since 0.1.23 reach the published npm package. Only package.json and package-lock.json change; no code is touched.

• Merging this PR does not publish anything. Push the v0.1.24 tag on main afterwards to trigger the release workflow, which builds the binaries and publishes npm.
• A workflow_dispatch release is not used because it would ship GitHub binaries at this version while leaving npm on 0.1.23.

^{Written for commit d39d0d4. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 2 files

_{View guided diff | Turn on auto-fix | Re-trigger cubic}

[jwfing]

LGTM - approved.