Refactor(material): Replace Hidden component

[LukasBoll]

Removes the deprecated hidden component and instead returns null if the hidden property is set.

Closes #2107

[netlify]

✅ Deploy Preview for jsonforms-examples ready!

Name	Link
🔨 Latest commit	e3a8a9f
🔍 Latest deploy log	https://app.netlify.com/sites/jsonforms-examples/deploys/661cfd1540bfc100090bbe2c
😎 Deploy Preview	https://deploy-preview-2315--jsonforms-examples.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coveralls]

coverage: 84.383% (-0.007%) from 84.39%
when pulling e3a8a9f on LukasBoll:remove_hidden
into b87f5b8 on eclipsesource:master.

[lucas-koehler]

Hi @LukasBoll , thank you for the contribution ❤️
Many of the refactoring already look good to me :) However, I discovered that you introduced new <div> elements at some places for the removed <Hidden> elements.
Is this really necessary? I think they are superfluous. If you just need a wrapper component to return multiple sibling elements, the React Fragment <>...</> can be used instead. This won't create an additional DOM element.

The files with introduced div I saw are:

• packages/material-renderers/src/additional/MaterialListWithDetailRenderer.tsx
• packages/material-renderers/src/complex/MaterialAllOfRenderer.tsx
• packages/material-renderers/src/complex/MaterialAnyOfRenderer.tsx
• packages/material-renderers/src/complex/MaterialArrayControlRenderer.tsx
• packages/material-renderers/src/complex/MaterialOneOfRenderer.tsx
• packages/material-renderers/src/controls/MaterialBooleanControl.tsx
• packages/material-renderers/src/controls/MaterialBooleanToggleControl.tsx
• packages/material-renderers/src/layouts/MaterialCategorizationLayout.tsx
• packages/material-renderers/src/layouts/MaterialCategorizationStepperLayout.tsx
• packages/material-renderers/src/mui-controls/MuiAutocomplete.tsx

For the MaterialAnyOfRenderer and the MaterialArrayControlRenderer I checked whether the removed <Hidden> resulted in a missing <div>. This turned out to be false. Instead the newly added <div> added in this PR was there on top. This suggests that the <div> is not necessary.

Please check whether wrapping in a <div> is really necessary for the aforementioned renderers. If not, use the react fragment <> instead to return multiple sibling elements.

[LukasBoll]

Hi @lucas-koehler ,
thanks for the review. Indeed I just wanted to wrap multiple elements. Thanks for the Fragment hint! I updated and tested the corresponding renderers the solution with the Fragment worked fine!

[lucas-koehler]

LGTM now. Thanks for the updates!