fix: pin cheerio

[pieh]

Description

cheerio recently was released as stable with set of breaking changes that previous RC version didn't have. One of the main ones is related to this cheeriojs/cheerio#3986 (comment) in

gatsby/packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js

Line 8 in 33f18ba

import cheerio from "cheerio"

which currently released wordpress plugin cause problems for users that are installing plugin manually now or tried to regenerate lock file / updated packages.

Because stable version requires node@>=18.17, it's not something that can be merged without the need to bump major for lot of packages, so instead of migrating wordpress plugin import, we are pinning to last available version before required node version was bumped. 1.0.0-rc.12 version I pinned to was also the version that has been in used by gatsby packages for over 2 years, so this pinning just stabilize it.

Underlying reason for ci/circleci: integration_tests_gatsby_cli failure is

error cheerio@1.0.0: The engine "node" is incompatible with this module. Expected version ">=18.17". Got "18.0.0"

Which is one of the things this PR is addressing, but because that test only use things actually released to npm and not current state of the repo it's not something that can be easily/quickly changed.

[pieh]

Successfully published:
 - gatsby-plugin-offline@6.13.3
 - gatsby-remark-copy-linked-files@6.13.2
 - gatsby-remark-graphviz@5.13.2
 - gatsby-remark-images-contentful@6.13.2
 - gatsby-remark-images@7.13.2
 - gatsby-remark-prismjs@7.13.2
 - gatsby-remark-responsive-iframe@6.13.2
 - gatsby-source-wordpress@7.13.5