[vaishakdinesh]

Bumps the tf-migrate formula from v1.0.0 to v1.1.1.

The formula has been pinned at v1.0.0 since April and has missed two releases
(v1.1.0, 2026-07-14 and v1.1.1, 2026-10-22). cf-terraforming did not drift
because the cf-terraforming repo has a bump-formula.yaml workflow that
auto-bumps this tap on release; tf-migrate has no equivalent workflow
(ci.yml, release.yml, semgrep.yml, supportability-matrix.yml only).
Adding one there is a sensible follow-up so this stops drifting — it needs a
BUMP_CASK_TOKEN secret provisioned in the tf-migrate repo first.

Verification

• sha256 computed independently from the release source tarball:
  69d39a0282aecce07d82a574082493ac8f6bd62c40ca728899cabd528fffb863
• Build assumptions still hold at v1.1.1: cmd/tf-migrate/main.go is
  package main and still declares var version = "dev", so both
  ./cmd/tf-migrate and -X main.version remain correct. The install
  and test blocks are unchanged.

Note on scope

This is a staleness fix, not a security fix. The recent Go toolchain work
(distrusting 8 revoked eMudhra intermediates, fixed in Go 1.27.3) is entirely
inside the Go standard library, and this formula builds from source with
depends_on "go" => :build. homebrew-core's go is currently 1.27.3 and this
tap ships no bottles, so every brew install already produced a patched binary
regardless of which tag was built — v1.0.0's go 1.25.1 directive is a minimum
and Go does not downgrade.

cf-terraforming.rb is deliberately untouched: it is already at v0.30.0 and its
recorded sha256 verifies against the source tarball.