Correctly set page prop back to 0 when resetPageOnUpdate is enabled

[cpba]

Otherwise if there is a server side search while we're on a page other than 0, the current page is set back to 0 but the prop retains its old value. Causing issues with server side pagination as the page number that the server receives is different from the one the client is displaying.

Fixes #1311

[mnsrulz]

@cpba i am noticing if you enable server side search with this change, each search is issuing two api calls instead of one. Perhaps a quick fix is to check if the props page value > 0 then only set it to 0?

[cpba]

Perhaps a quick fix is to check if the props page value > 0 then only set it to 0?

Yes, that would work. I think it'd still fire two calls if the search is started from a different page, but that'll only happen once so perhaps it isn't very important.

I'll make the change.

[mnsrulz]

I think it'd still fire two calls if the search is started from a different page, but that'll only happen once so perhaps it isn't very important.

Totally inline with that. There might be a better way to eliminate it which @afshinm can guide…