Document that paging state is sensitive to protocol version + expose "unsafe" API

Description

One detail we overlooked while adding the paging state in 2.0.10 is that it's protocol-dependent, in that a paging state computed with protocol v2 won't work with protocol v3. That's because we hash the serialized form of the query parameters to compute the hash.

This should be mentioned in the documentation. Also, we should expose an "unsafe" API that works with the raw bytes, for users who want a workaround (it will be up to them to implement there own validation logic).

Environment

None

Pull Requests

None
Fixed

Assignee

Olivier Michallat

Reporter

Olivier Michallat

Labels

None

PM Priority

None

Affects versions

Fix versions

Pull Request

None

Doc Impact

None

Size

None

External issue ID

None

External issue ID

None

Priority

Minor
Configure