[UBER-829] Avoiding redundant table model rebuilding

[sol-0]

Contribution checklist

Brief description

https://front.hc.engineering/workbench/platform/tracker/UBER-829

• caching model options in Table to avoid model rebuilding and re-rendering

Checklist

• - UI test added to added/changed functionality?
• - Screenshot is added to PR if applicable ?
• - Does the code work? Check whether function and logic are correct.
• - Does Changelog.md is updated with changes?
• - Does the translations are up to date?
• - Does it well tested?
• - Tested for Chrome.
• - Tested for Safari.
• - Go through the changed code looking for typos, TODOs, commented LOCs, debugging pieces of code, etc.
• - Rebase your branch onto master and upstream branch
• - Is there any redundant or duplicate code?
• - Are required links are linked to PR?
• - Does new code is well documented ?

Related issues

A list of closed updated issues

[haiodo]

@sol-0 why we need to restore scroll position? if we show panel on top of all content, it should be not touched. So please check a bit more.

[sol-0]

@sol-0 why we need to restore scroll position? if we show panel on top of all content, it should be not touched. So please check a bit more.

I've looked for root cause once again and found out that table model was rebuilding every time that caused table re-rendering. Now we're caching the results and checking the changes in model options before rebuilding the model.