chore: remove example/v9.x.x code

[ripecosta]

Description

Removes all the examples/v9.x.x code. They are triggering security alerts (like this one) and are already backed up in the v9.x.x branch.

Fixes #1786

Checklist

• only relevant code is changed (make a diff before you submit the PR)
• run tests npm run test
• tests are included
• commit message and code follows the Developer's Certification of Origin

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/i18next-browser-languagedetector@8.0.0	None	+2	371 kB	adrai
npm/i18next-http-backend@2.5.2	network	+2	363 kB	adrai
npm/i18next@23.11.5	None	+2	925 kB	adrai

🚮 Removed packages: npm/babel-preset-razzle@4.0.5, npm/express@4.17.1, npm/html-webpack-plugin@5.3.1, npm/i18next-browser-languagedetector@6.1.2, npm/i18next-fs-backend@1.1.1, npm/i18next-http-backend@1.2.8, npm/i18next-http-middleware@3.1.4, npm/mini-css-extract-plugin@1.4.1, npm/razzle-dev-utils@4.0.5, npm/razzle@4.0.5, npm/react-i18next@11.11.3, npm/react-router-dom@5.2.0, npm/serve@11.3.2

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	CI
Install scripts	npm/core-js@3.21.1	Install script: postinstall Source: node -e "try{require('./postinstall')}catch(e){}"	🚫
Install scripts	npm/core-js-pure@3.21.1	Install script: postinstall Source: node -e "try{require('./postinstall')}catch(e){}"	🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/core-js@3.21.1
• @SocketSecurity ignore npm/core-js-pure@3.21.1

[coveralls]

coverage: 97.094%. remained the same
when pulling c227c01 on ripecosta:rc/rm-example-v9
into 2f96833 on i18next:master.