add missing dependencies react/vue for next, ^13.0.0 versions

[evanSe]

Context

It is not possible to run some of the demos in stackblitz, namely for react/vue in the next & ^13.0.0 versions.

In the future we can fix other versions, just very tedious

How has this been tested?

going to the following URLs and seeing that they load and are functional

https://stackblitz.com/github/evanSe/handsontable/tree/develop/examples/next/docs/react/demo
https://stackblitz.com/github/evanSe/handsontable/tree/develop/examples/next/docs/vue/demo

https://stackblitz.com/github/evanSe/handsontable/tree/develop/examples/13.1.0/docs/react/demo
https://stackblitz.com/github/evanSe/handsontable/tree/develop/examples/13.1.0/docs/vue/demo

https://stackblitz.com/github/evanSe/handsontable/tree/develop/examples/13.0.0/docs/react/demo
https://stackblitz.com/github/evanSe/handsontable/tree/develop/examples/13.0.0/docs/vue/demo

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature or improvement (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Additional language file or change to the existing one (translations)

Affected project(s):

• handsontable
• @handsontable/angular
• @handsontable/react
• @handsontable/vue
• @handsontable/vue3

Checklist:

• I have reviewed the guidelines about Contributing to Handsontable and I confirm that my code follows the code style of this project.
• I have signed the Contributor License Agreement
• My change requires a change to the documentation.

[budnix]

@evanSe The examples for version 13.0.0 fail because there is a missing NODE_OPTIONS=--openssl-legacy-provider option (required by webpack on >Node 16). I'd propose reverting the changes for 13.0.0 and leaving them for 13.1.0 and next or adding the openssl-legacy-provider flag to all demos.

[evanSe]

@evanSe The examples for version 13.0.0 fail because there is a missing NODE_OPTIONS=--openssl-legacy-provider option (required by webpack on >Node 16). I'd propose reverting the changes for 13.0.0 and leaving them for 13.1.0 and next or adding the openssl-legacy-provider flag to all demos.

Went with the legacy provider route as we already have some using it