feat: add additional column ordering to keysetpagination

[jonas-jonas]

cc @zepatrik

Related Issue or Design Document

Checklist

• I have read the contributing guidelines and signed the CLA.
• I have referenced an issue containing the design document if my change introduces a new feature.
• I have read the security policy.
• I confirm that this pull request does not address a security vulnerability.
  If this pull request addresses a security vulnerability,
  I confirm that I got approval (please contact [email protected]) from the maintainers to push the changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have added the necessary documentation within the code base (if appropriate).

Further comments

[zepatrik]

Nice, this already looks very good 👍
Should we maybe allow multiple additional fields? We might not use it, but then it will be easy to do once it comes up.

[jonas-jonas]

@zepatrik I'd like to postpone the support for multiple fields for now. I've spent too much time on this already, and that would just complicate it, IMO. I'll add some more tests, but then it should be good to go.

[zepatrik]

Suggested change

	type PageTokenConstructor func(string) (PageToken, error)
	type PageTokenConstructor = func(string) (PageToken, error)

A type alias allows to just pass a value without ever needing to do type assertions.

[jonas-jonas]

Ah, nice. Don't think this changes much in the current PR. Or did you have something specific in mind?

[zepatrik]

Nice 🎉