fix(gatsby-plugin-sitemap): Add plugin options forbidden for deprecated exclude

[orta]

In gatsby-plugin-sitemap 3 - > 4 exclude turned into excludes but the error message looked like:

Error: Body must be a string. Received: undefined.

For the old config. Given that most people would probably upgrade like I did via "Gatsby 2->3" and all libraries with it, I read the migration for Gatsby but not each official plugin.

I resisted the temptation to randomly duckduckgo for the error message on this one for a while, but the message was a red herring. Eventually I gave up and found #31416 (comment) - so this should give a better error message for folks migrating.

[LekoArts]

Thanks for the PR!

I've changed it to use our Plugin Options API: https://www.gatsbyjs.com/docs/how-to/plugins-and-themes/configuring-usage-with-plugin-options/

We've got a section on deprecating options there (sadly it wasn't done in the initial PR): https://www.gatsbyjs.com/docs/how-to/plugins-and-themes/configuring-usage-with-plugin-options/#deprecating-options

It'll then also immediately fail:

ERROR #11331  PLUGIN

Invalid plugin options for "gatsby-plugin-sitemap":

- As of v4 the `exclude` option was renamed to `excludes`

not finished open and validate gatsby-configs, load plugins - 0.256s

error Command failed with exit code 1.

[orta]

Works for me, thanks!

[luckpot207]

I m in cli command: gatsby develop
then some error happenend

warn Plugin gatsby-source-hubspot is not compatible with your gatsby version 4.1.3 - It requires gatsby@<3.0.0

ERROR #11331 PLUGIN

Invalid plugin options for "gatsby-source-prismic":

• gatsby-source-prismic(ellipsis-drive) - JSON model for "episode" is missing. If the Custom Type is no longer in use, you
  may provide "{}" as the JSON model.
• gatsby-source-prismic(ellipsis-drive) - JSON model for "article_cta" is missing. If the Custom Type is no longer in use,
  you may provide "{}" as the JSON model.

not finished open and validate gatsby-configs, load plugins - 1.543s