Invalid deserialization when paging a rowset and a schema change happens

Description

This affects native protocol v5 and DseV2 so Apache Cassandra 4.0+ and DSE 6.0+

paging_state comes before new_metadata_id as mentioned in https://issues.apache.org/jira/browse/CASSANDRA-13986 but it is being read from the frame in the reverse order.
When both flags are set on the response, the deserialization will be invalid because of this.

Environment

None
Fixed

Assignee

Unassigned

Reporter

Joao Reis

Fix versions

Sprint