fix: make refreshACM send its acm_refresh body so cert auto-refresh works over the SDK

[jdodson]

Summary

Makes the generated refreshACM method actually send its request body, so PATCH /apps/{id}/acm includes {acm_refresh: true } instead of an empty body. This unblocks migrating the CLI's certs:auto:refresh command onto the SDK.

Why, is something broken?

The upstream hyperschema's "Refresh ACM" link ships with no schema block, so the generator never emitted a requestBody param or the hasRequestBody route flag... and the SDK dropped the body.

This fix started in Slack in this discussion: https://salesforce-internal.slack.com/archives/C048U82QVKQ/p1784568350711309?thread_ts=1784204631.074229&cid=C048U82QVKQ

Type of Change

Breaking Changes (major semver update)

• Add a ! after your change type to denote a change that breaks current behavior

Feature Additions (minor semver update)

• feat: Introduces a new feature to the codebase

Patch Updates (patch semver update)

• fix: Bug fix
• deps: Dependency upgrade
• revert: Revert a previous commit
• chore: Change that does not affect production code
• refactor: Refactoring existing code without changing behavior
• test: Add/update/remove tests

Testing

CI only runs npm test (and not on the PR itself), so please run this locally to verify:

• npm test # 127/127, includes the golden byte-for-byte test — the real correctness gate
• npm run typecheck # clean (CI does NOT run this)
• grep -A3 '"refreshACM"' dist/3.sdk/routes.js # shows "hasRequestBody": true
• grep -n AppRefreshACMOpts dist/3.sdk/types.d.ts # interface + param present

Screenshots (if applicable)

Related Issues

GUS work item: https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE00002eHYVDYA4/view

[k80bowman]

Nicely done. Looks good.