Add React hooks section to code style guide

[AWolf81]

Description

As mentioned in the issue I'd like to add a usage info for React Hooks.

I've copied the discussion part from the issue to the PR (see below)

Issue fixed

#2999

Type of changes

• ⚪ Bug fix (Change that fixed an issue)
• ⚪ Breaking change (Change that can cause existing functionality to change)
• ⚪ Improvement (Change that improves the code. Maybe performance or development improvement)
• ⚪ Feature (Change that adds new functionality)
• 🔘 Documentation change (Change that modifies documentation. Maybe typo fixes)

Checklist:

• ⚪ My code follows the project code style
• ⚪ I have written test for my code and it has been tested
• ⚪ All existing tests have been passed
• ⚪ I have attached a screenshot/video to visualize my change if possible

Discussion

• Do we need a special heading to the copy? Right now I would add React Hooks as heading.
• My personal opinion is that I would use hooks if it improves reusability e.g. a useResize would be easier to read / understand than a listener for resize event in the constructor or componentDidMount of a class based component. Both implementations are OK and I'm not seeing it as a must have to use hooks - I would prefer class-based components. What is your opinion? Recommend to continue to use class-based components or always use hooks or use both as I'd recommend?
• I'm not sure about the point with mixing functional and class-based with-in a feature (2nd last sentence in the copy) - maybe that's also OK to use. What do you think? Maybe I have to create an example to see if it's also OK.
• Anything else to add to the copy?

[ZeroX-DG]

LGTM 🎉