fix(engines): Revert engine back to 16

[benmvp]

#430 upgraded the Node version to 18, but as a fix released in 4.1.4 (instead of as a breaking change). So it breaks consumers of the library (such as semantic-release) that are still on Node 16.

Resolves #431

---

Behavior

Before the change?

• Able to install a package using @ocktokit/plugin-retry with Node 16.

After the change?

• Unable to install a package using @ocktokit/plugin-retry with Node 16 because it requires Node 18.

Other information

n/a

---

Additional info

Pull request checklist

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Added the appropriate label for the given change

Does this introduce a breaking change?

It doesn't. The previous PR did

Please see our docs on breaking changes to help!

• Yes (Please add the Type: Breaking change label)
• No

If Yes, what's the impact:

• N/A

Pull request type

Please add the corresponding label for change this PR introduces:

• Bugfix: Type: Bug
• Feature/model/API additions: Type: Feature
• Updates to docs or samples: Type: Documentation
• Dependencies/code cleanup: Type: Maintenance

---

[wolfy1339]

Can you also update the build script: scripts/build.mjs to use node 16

[benmvp]

Can you also update the build script: scripts/build.mjs to use node 16

done and done!

[github-actions]

🎉 This PR is included in version 4.1.5 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[benmvp]

Thanks for being so responsive @wolfy1339! 🎉 Such a quick turnaround 🙏🏾

[benmvp]

Verified that 4.1.5 fixes things!