Destroy TabularData in RecordSelector, TablePage, and TableWidget to prevent Memory leaks

[pavish]

Description

• There are a lot of places (eg.,RecordSelector, TablePage, and TableWidget) where TabularData object is created reactively, like this:

  $: tabularData = new TabularData({
   id: table.id,
   abstractTypesMap,
   meta,
  });
  

This creates a new instance each time any of the arguments get updated, and is never destroyed, leading to memory leaks. Each TabularData instance should be destroyed before the next instance is created.

If possible, we should consider the following improvements:

• The TabularData instance creation is costly and should be kept to a minimum, if possible it should not be made reactive.
• We should update a TabularData's property instead of recreating if it is possible.

[seancolsen]

@pavish Can we move this to a later milestone, or is there a reason this affects the live demo?

[pavish]

Ah, I was creating a number of issues and must have placed this in Live demo by mistake. I wanted this to be in the first release. I'll change the milestone.