Adds persistence and reloading of datatable pagination params

[pavgra]

fixes #760

[anthonysena]

@pavgra just testing this out and it seems like what you've built here works well for the data table component itself. That said, it looks like perhaps the other parts of the application need to be more aware of the state of the data table. Take for example the following workflow:

• Navigate to the cohort definition list via the left-hand menu
• Filter the list using the search which results in a URL like: http://localhost:81/atlas/#/cohortdefinitions?dtSearch_-1258431457=ehden&dtPage_-1258431457=0
• Open a cohort definition from that list
• Close the cohort definition

I'd expect that closing the cohort definition would preserve the query string parameters required to filter the data table contents but that seems to get lost in the process. Could you take a look or let me know if you need any further details? Thanks!

[pavgra]

@anthonysena , I do not think that this case can be implemented in a straightforward and clean way:

• after you navigated to a specific cohort definition, you may go over tabs back and forward, go into vocabulary search to attach concepts, etc - so, it is impossible to assign a browser's back button behavior to the close button
• therefore, we would need to store pagination parameters of the previous page:
  • either we can attach them to cohort definition URL - that would be /cohortdefinition/111?searchParamOfTableFromPrevPage=... - but that would make links really ugly and the logic very non-trivial
  • or we could put the params into sessionStorage; however, that would lead to the different behavior of the same page for different users, i.e. you wouldn't be able to share a link and expect the app to behave in the same way (since it would depend on your local data)

[anthonysena]

I'd like to confirm with @gklebanov around the functional requirements for #760 before we merge this into master.