perf: implement shouldOnCreateNode for all our plugins/benchmarks

[pvdz]

This is a followup for #27442 which introduced a shouldOnCreateNode API to test whether the async onCreateNode callback ought to be called.

This PR implements this hook for all the plugins in our monorepo and some benchmark sites.

For all plugins, the behavior should remain the same and should be backwards compatible since the check also exists in the onCreateNode hook itself.

If a plugin happens to break, anyways, please try to fix forward rather than revert this whole PR. Thanks :)

[vladar]

Looks good to me. Left one question but nothing blocking this.

[LekoArts]

Other than the benchmark inconsistencies (mentioned in Slack) LGTM
Small typo but other than that you consistently moved the exports in the same order, same checks in plugins 👍

[pvdz]

Published as part of one of the following:

 - gatsby-plugin-feed@2.5.17
 - gatsby-plugin-image@0.0.4
 - gatsby-plugin-mdx@1.2.49
 - gatsby-plugin-netlify@2.3.22
 - gatsby-plugin-offline@3.2.35
 - gatsby-plugin-sass@2.3.19
 - gatsby-plugin-typescript@2.4.23
 - gatsby-plugin-utils@0.2.37
 - gatsby-react-router-scroll@3.0.15
 - gatsby-remark-custom-blocks@2.3.14
 - gatsby-remark-images@3.3.37
 - gatsby-source-contentful@3.0.1
 - gatsby-transformer-asciidoc@1.3.15
 - gatsby-transformer-csv@2.3.14
 - gatsby-transformer-documentationjs@4.3.17
 - gatsby-transformer-excel@2.4.16
 - gatsby-transformer-hjson@2.4.14
 - gatsby-transformer-javascript-frontmatter@2.3.15
 - gatsby-transformer-javascript-static-exports@2.4.14
 - gatsby-transformer-json@2.4.15
 - gatsby-transformer-pdf@1.3.15
 - gatsby-transformer-react-docgen@5.2.15
 - gatsby-transformer-remark@2.8.44
 - gatsby-transformer-screenshot@2.3.20
 - gatsby-transformer-sharp@2.5.19
 - gatsby-transformer-toml@2.4.17
 - gatsby-transformer-xml@2.3.15
 - gatsby-transformer-yaml@2.4.15
 - gatsby@2.24.83