Virtualize rendering of result in ResultContainer

[rmanaem]

At the moment using the select-all checkbox leads to re-rendering all ResultCard components which takes 1-2 seconds and affects the user experience.

As part of addressing #17 we've tried using

• react-window
  • Its FixedSizeList requires a fixed size for all cards which in our case doesn't work since cards have different content
  • its VariableSizeList comes short and isn't able to handle the card sizes well
• react-virtualized
  • suffers from a bogus import that seem to have been around since 2021, see the original issue and its successor
  • The plugin fix mentioned in npm es module result do not have bpfrpt_proptype_WindowScroller in WindowScroller/onScroll.js, bvaughn/react-virtualized#1722 works fine but the Cypress GH action for component test doesn't like it. See
• Virtuoso
• works well out of the box but it breaks the e2e tests with a ResizeObserver loop completed with undelivered notifications error

Our options from here are:

• Set a fixed size for all cards and use FixedSizeList which is not guaranteed to break tests or CI as it never got to that point
  • good resource to check for this option: https://blog.logrocket.com/react-virtualized-vs-react-window/
• Be zen and leave it be

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!

[surchs]

The performance issue was addressed by #39 with memoization, however the virtualization issue could still be addressed if it becomes a performance bottleneck again