Add CLI push guards, safety checks, quiet duration, and format/lint caching

[tjementum]

Summary & Motivation

Add a banned-push-words CLI command that lets developers configure words that must not appear in pushed diffs. The pre-push hook normalizes both the diff and the word list (lowercasing, stripping spaces/hyphens/underscores) so that any casing or separator variant is caught. Enforcement can optionally be scoped to specific remotes.

• Block running the published CLI alias from a repository or worktree other than the one it was built from, preventing accidental cross-repo execution
• Save the Aspire dashboard login URL to .workspace/aspire-dashboard-url.txt on startup so other tools can discover it without parsing logs
• Show command duration in --quiet mode output for build, format, lint, and e2e commands
• Add source state caching to format and lint commands so redundant runs are skipped when no code has changed since the last successful run
• Update the deploy command confirmation prompt to list all three disabled workflows (Deploy Container, Deploy Infrastructure, and Migrate Database)
• Clean up a comment in EndpointMetadataTests that referenced specific downstream project names

Checklist

• I have added tests, or done manual regression tests
• I have updated the documentation, if necessary

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud