Point the README examples at v0.15.0

[jlaneve]

Description

The README tells people to use astronomer/deploy-action@v0.14.0, in 20 places. #161 has merged, so the next tag is v0.15.0 and the examples should point at it.

Merge this and cut the v0.15.0 tag together. Until the tag exists, these examples reference a ref that does not resolve — which is how #157 and #158 went in July.

v0.15.0 carries one behaviour change worth naming in the release notes: cli-version now defaults to 1.45.0 rather than empty. Empty meant the installer picked, which resolved to a hardcoded constant on astro-cli's main and lagged real releases by anywhere from 9 minutes to 13 days. 1.45.0 is the version an unpinned run installs today, so nobody's CLI moves on upgrade — it is stated now rather than inferred, and it stays put until someone bumps it.

Anyone who wants to track the newest CLI has no option in v0.15.0. That is a real gap, and the follow-up adds cli-version: latest as an explicit opt-in. It needs astro-cli v1.46.0 first, since it reads the install.sh asset that astronomer/astro-cli#2252 publishes and no released version carries one yet.

🎟 Issue(s)

None.

🧪 Functional Testing

Docs only, and the diff is one string repeated. No 0.14.0 references remain.

📸 Screenshots

N/A.

📋 Checklist

• Rebased from the main (or release if patching) branch (before testing)
• Ran make test before taking out of draft — no code changed
• Ran make lint before taking out of draft — no code changed
• Added/updated applicable tests — docs only
• Tested against Astro-API (if necessary).
• Tested against Houston-API and Astronomer (if necessary).
• Communicated to/tagged owners of respective clients potentially impacted by these changes. — the prospect waiting on this pins @v0.14.0, so they need to move to @v0.15.0 once tagged; nothing landing on main reaches them before that
• Updated any related documentation — this is that change; the docs site references install.astronomer.io, which is unaffected