@W-21386533 MCP MRT Push now uses correct defaults based on detected project type

[patricksullivansf]

Summary

This fixes the MRT Push tool implemented with #110 to use project type aware defaults for the bundling step. This is necessary because the MRT Bundles for sfnext won't start with the default bundle glob patterns.

Testing

Use the testing setup from #110 but be sure to deploy the MRT project to an environment and verify it starts without error. Repeat the test for a pwv3 and sfnext project.

Dependencies

• No net-new third-party dependencies were added
• If net-new third-party dependencies were added, rationale/discussion is included and 3pl-approved is set by a maintainer

---

• Tests pass (pnpm test)
• Code is formatted (pnpm run format)

[yhsieh1]

@patricksullivansf The PR looks good. Are you able to test it out?

[patricksullivansf]

@patricksullivansf The PR looks good. Are you able to test it out?

• Tested with sfnext template app deployed with MCP MRT Push tool. It also required having the 4 mandatory ENV vars set (the error state appears the same for missing env as bad bundle, unless looking at MRT logs).
• Tested with pwa kit v3 generated app.

There's a side discussion on ssrFunctionNodeVersion we might fold into this PR before we merge.

[yhsieh1]

@patricksullivansf The PR looks good. Are you able to test it out?

• Tested with sfnext template app deployed with MCP MRT Push tool. It also required having the 4 mandatory ENV vars set (the error state appears the same for missing env as bad bundle, unless looking at MRT logs).
• Tested with pwa kit v3 generated app.

There's a side discussion on ssrFunctionNodeVersion we might fold into this PR before we merge.

FYI: You could either use npx @salesforce/pwa-kit-dev@latest tail-logs --project [your project] --environment [target env] or b2c mrt tail-logs -p <project> -e <environment> to get MRT logs