Monokle: improve speed performance

[chlete]

As a user I would like that Monokle opens faster my large set of projects:

• [x] Add virtualization to the SectionBlueprintRenderer
• [ ] Improve the shallow compare of section blueprint middleware
• [ ] Avoid dispatching unnecessary actions (use debounce where it makes sense)
• [ ] Replace uses of useEffect + useState with useMemo

[chargio]

Separate file management from resource management, because the main use case is to process and edit files, beyond generating a list of resources. Also, being able to quickly provide a responsive environment generates a way better user experience and reduce the possibility for the user to decide to use vim instead of Monokle if the interface takes too long to update before it is ready to accept inputs.

• Opening folder and then showing files in the hierarchy can be done really quickly, without processing the files to find resources. This allows the user to quickly start selecting files and editing them, not waiting for the full process to happen, something that can take more than a minute.
• Then a background process can populate and update the resource panel. Additional optimizations (like prioritizing the folder where the resource is stored), can be used to show accurate results earlier.
• This allows the user to select a folder and start using the editor, so processing of that file (syntax highlighting and identifying resources) should be prioritized for that file.

That is similar to other editors, that work this way, our current process can be too slow for engineers that need a quick feedback loop