React wrapper: Wrap internal utilities into a context provided from HotTable to its children

[NOtherDev]

Context

Changing the way HotTable communicates with HotColumns below. Right now, to avoid props passing and expose simple <HotTable ...><HotColumn ... /></HotTable> children-based API, the utilities are shared from HotTable to HotColumn via React.Children iteration and cloneElement "magic". We agreed it's not idiomatic React and React way to do it would be to use context.

However, it turned out that besides shared utils, the HotColumn instances get columnIndex prop which obviously its different for each children, so the only way to do it without forcing end-users to specify these indices is to keep a part of the current approach.

I also skipped moving hotInstance access to the context as right now there's no need to do so. HotInstance is initialized and accessed only from HotTable - moving it elsewhere will only introduce unnecessary complexity.

How has this been tested?

• All the unit tests still pass. No new unit tests as this is an internal structural change with no intention to be observable from the outside.
• Example projects from the repo still work properly.

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)

☝️ actually, none of them. This is purely a structural change with no behavior change intended.

Related issue(s):

1. Proposal in RFC
2. Already pre-reviewed discussion with @evanSe in my private fork

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.