add support for nested keys in useInfiniteQuery's pageParamKey

[rsbh]

In our backend APIs, the page/offset key is not at the root level. Instead, it is nested inside the query key, e.g.

{
    "query": {
        "search": "",
        "page": 1
        "sort": {
            "key": "name",
            "order": "asc"
        }
    }
}

We were using version 2.1.1 before and set query as pageParamKey. It was working before. but after these changes , they stopped working.

An ideal fix will be to add support for nested keys in pageParamKey, e.g., query.page

[paul-sachs]

@rsbh Thanks for logging it. The handling of page param key is a little wonky, so I think what you've mentioned here probably make sense. I'm open to PRs if you want to give it a whirl, otherwise I'll try to get around to it sometime. The typing is a little tricky but nothing that hasn't been done before I think.

[rsbh]

Yes, using type string for pageParamKey can make it easy. I was trying to add support for dot notation with TS.