ScrollTop and ScrollLeft state should be componentStates to avoid side effects

[charlesBochet]

Scope & Context

While refactoring ScrollWrapper component, we have recently introduced two states: ScrollTop and ScrollLeft. These states should be componentState so each ScrollWrapper instance does have its own state. Otherwise they are all interacting together, creating re-renders

How:

In scrollLeftState (same for scrollTopState)

• Rename it to scrollLeftComponentState, and use createComponentState instead of createState
• introduce useScrollStates hook that will only extractComponentState and take a scrollWrapperId as a parameter. See useViewStates for an example.
• replace direct import of scrollLeftState by call to useScrollStates

[Jeetch8]

I want to take on this issue. Can you please assign it to me ?

[charlesBochet]

Sure! Thank you @Jeetch8

[Jeetch8]

I have created the PR. Please check #4938

[charlesBochet]

Thank you, taking a look!

[FelixMalfait]