fix(deps): update dependency google-map-react to v2.2.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
google-map-react	2.1.8 -> 2.2.1

---

Release Notes

google-map-react/google-map-react (google-map-react)

v2.2.1

Compare Source

v2.2.0

Compare Source

v2.1.10

Compare Source

• #​1028 Update peerDependencies for React 17

v2.1.9

Compare Source

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻️ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you check the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @multei/web@0.1.0
npm ERR! Found: react@17.0.1
npm ERR! node_modules/react
npm ERR!   react@"17.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.0.0" from google-map-react@2.1.9
npm ERR! node_modules/google-map-react
npm ERR!   google-map-react@"2.1.9" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2021-04-26T12_49_40_889Z-debug.log

[netlify]

❌ Deploy preview failed at Netlify. @jimmyandrade take a look please

Name	Link
🔨 Latest commit	9fb92c0
🔍 Latest deploy log	https://app.netlify.com/sites/multei/deploys/66ca6bd5fd4a7100083e9cd9

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm notice 
npm notice New major version of npm available! 8.19.4 -> 9.6.7
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.7>
npm notice Run `npm install -g npm@9.6.7` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @hot-loader/react-dom@17.0.0
npm ERR! Found: react@17.0.1
npm ERR! node_modules/react
npm ERR!   react@"17.0.1" from the root project
npm ERR!   peer react@">=16.3.0" from @emotion/core@10.0.35
npm ERR!   node_modules/@emotion/core
npm ERR!     peer @emotion/core@"^10.0.27" from @emotion/styled@10.0.27
npm ERR!     node_modules/@emotion/styled
npm ERR!       peer @emotion/styled@"^10.0.14" from gatsby-interface@0.0.193
npm ERR!       node_modules/gatsby-interface
npm ERR!         gatsby-interface@"^0.0.193" from gatsby-recipes@0.2.33
npm ERR!         node_modules/gatsby-recipes
npm ERR!       1 more (gatsby-recipes)
npm ERR!     peer @emotion/core@"^10.0.28" from @emotion/styled-base@10.0.31
npm ERR!     node_modules/@emotion/styled-base
npm ERR!       @emotion/styled-base@"^10.0.27" from @emotion/styled@10.0.27
npm ERR!       node_modules/@emotion/styled
npm ERR!         peer @emotion/styled@"^10.0.14" from gatsby-interface@0.0.193
npm ERR!         node_modules/gatsby-interface
npm ERR!         1 more (gatsby-recipes)
npm ERR!     3 more (gatsby-interface, gatsby-recipes, theme-ui)
npm ERR!   15 more (@emotion/styled, @emotion/styled-base, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"17.0.0" from @hot-loader/react-dom@17.0.0
npm ERR! node_modules/@hot-loader/react-dom
npm ERR!   dev @hot-loader/react-dom@"17.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@17.0.0
npm ERR! node_modules/react
npm ERR!   peer react@"17.0.0" from @hot-loader/react-dom@17.0.0
npm ERR!   node_modules/@hot-loader/react-dom
npm ERR!     dev @hot-loader/react-dom@"17.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/worker/32a1d6/0c464a/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/32a1d6/0c464a/cache/others/npm/_logs/2023-05-30T18_43_38_200Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @hot-loader/react-dom@17.0.0
npm ERR! Found: react@17.0.1
npm ERR! node_modules/react
npm ERR!   react@"17.0.1" from the root project
npm ERR!   peer react@">=16.3.0" from @emotion/core@10.0.35
npm ERR!   node_modules/@emotion/core
npm ERR!     peer @emotion/core@"^10.0.27" from @emotion/styled@10.0.27
npm ERR!     node_modules/@emotion/styled
npm ERR!       peer @emotion/styled@"^10.0.14" from gatsby-interface@0.0.193
npm ERR!       node_modules/gatsby-interface
npm ERR!         gatsby-interface@"^0.0.193" from gatsby-recipes@0.2.33
npm ERR!         node_modules/gatsby-recipes
npm ERR!       1 more (gatsby-recipes)
npm ERR!     peer @emotion/core@"^10.0.28" from @emotion/styled-base@10.0.31
npm ERR!     node_modules/@emotion/styled-base
npm ERR!       @emotion/styled-base@"^10.0.27" from @emotion/styled@10.0.27
npm ERR!       node_modules/@emotion/styled
npm ERR!         peer @emotion/styled@"^10.0.14" from gatsby-interface@0.0.193
npm ERR!         node_modules/gatsby-interface
npm ERR!         1 more (gatsby-recipes)
npm ERR!     3 more (gatsby-interface, gatsby-recipes, theme-ui)
npm ERR!   15 more (@emotion/styled, @emotion/styled-base, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"17.0.0" from @hot-loader/react-dom@17.0.0
npm ERR! node_modules/@hot-loader/react-dom
npm ERR!   dev @hot-loader/react-dom@"17.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@17.0.0
npm ERR! node_modules/react
npm ERR!   peer react@"17.0.0" from @hot-loader/react-dom@17.0.0
npm ERR!   node_modules/@hot-loader/react-dom
npm ERR!     dev @hot-loader/react-dom@"17.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-08-24T23_24_54_419Z-debug-0.log