Stricten Eslint rules

[TomasEng]

As the team is growing, we need to stricten our Eslint rules in order to ensure that the code stays consistent and conforms with our principles.

We already have some open issues for particular rules:

• Apply lint rule for return types #13465
• Add linting for when to use relative paths #12191

Here are some other rules that we should consider:

Plugin	Rule	What to use it for
	max-params	Never exceed three parameters in a function
	max-depth	Only allow one level of abstraction
	max-nested-callbacks	Similar to max-depth, but for functions used as parameters
	max-lines	Split up in several files when a file becomes too large
	max-lines-per-function	Split up in several functions when a function becomes too large
typescript-eslint	no-explicit-any	Avoid using the any type
typescript-eslint	typedef	Require type annotations in certain places
eslint-plugin-react	function-component-definition	Enforce components to be written as function declarations
eslint-plugin-react	forward-ref-uses-ref	Ensure that the ref is forwarded when using forwardRef
eslint-plugin-react	hook-use-state	Enforce the naming convention for the return value of useState
eslint-plugin-import	no-cycle	Avoid circular dependencies

The rules may be applied one by one and to one package at a time if it turns out that they require a lot of changes in the code.