@W-21199544 MCP respect working-directory flag in cartidge and mrt tools

[patricksullivansf]

Summary

This addresses some caveats from #110 and #158

• MCP Tools for MRT Push and Cartridge Deploy respect working-directory flag (renamed startDir as workingDirectory; MCP Tools can use the helper services.getWorkingDirectory()).
• Reload the config settings before every tool call. This allows changes to project.json, dw.json etc. to be picked up without having to quit and restart cursor IDE.

Testing

In general repro the steps from #110 and #158 and observe the caveats are addressed.

• The MRT push tool finds the default build folder without having to explicitly set the build path.
• The MRT push tool picks up changes to package.json and .mobify files without restarting the IDE.
• The cartridge deploy tool finds the dw.json file in the expected root (under cartridges)
• The cartridge deploy tool picks up changes to dw.json without restarting the IDE.

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)

[patricksullivansf]

maybe this needs a changeset too? it's a bit breaking...

[clavery]

passed internally as startDir for pre-existing unknown reasons

Yuming wrote it as startDir so if this doesn't make sense (it's not a good name to me) we should align the value to workingDirectory and refactor

[patricksullivansf]

passed internally as startDir for pre-existing unknown reasons

Yuming wrote it as startDir so if this doesn't make sense (it's not a good name to me) we should align the value to workingDirectory and refactor

Aggressively renamed startDir as workingDirectly. LNK if you prefer I scale some renaming back such as the arguments to findDwJson

[clavery]

As long as tests pass I'm happy. workingDirectory is clear to me