fix: repair API doc generation by reverting replace-in-file dependency

[pepopowitz]

Description

#4673 bumped replace-in-file to a version that is incompatible with our API generators! This PR reverts to a version that works.

Why did we bump to a version that didn't work?

Honestly, I have no idea why #4673 didn't fail when I tested it locally. It obviously won't work -- the release notes make it clear that it has been rewritten as an ES module, which our code can not run. I didn't read those notes when I tested locally, which I should have....but I definitely tested locally, and I guess I must not have run npm install when I did. I tried, I really did! 😭

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.

• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

• My changes require a docs infrastructure review.