Rename --update to --no-cache on mpak run

[mgoldsborough]

Summary

• Renames the --update flag to --no-cache on mpak run / mpak bundle run for better developer ergonomics
• --no-cache is the idiomatic flag name (npm, pip, docker) and better describes the behavior — especially with --local where there's no registry update involved
• Renames RunOptions.update to RunOptions.noCache and normalizes Commander.js --no-* boolean in both action handlers

Test plan

• pnpm build passes
• All 133 tests pass
• mpak run --help shows --no-cache, no --update
• mpak run --no-cache --local <bundle> forces re-extraction

[shwetank-dev]

@mgoldsborough

Currently --update does 2 things:

1. Updates the cache with the latest version
2. Then runs the server

Do we want --no-cache to do the same 2 things. Or --no-cache will just run the latest server without caching it.

[mgoldsborough]

@mgoldsborough

Currently --update does 2 things:

1. Updates the cache with the latest version
2. Then runs the server

Do we want --no-cache to do the same 2 things. Or --no-cache will just run the latest server without caching it.

Good point. this is more about ergonomics for the user. The use case i had was a local mcp bundle. I was rebuilding the bundle with new code, but the exploded directory was still being cached. So we need a means to basically remove the unziped version