Create a stub API for next_raw_key_value_batch, which just returns the next key-value pair from the cursor, setting *returned_countp to 1 in the event of success. If there are no more rows in the table, the call should set *returned_countp to 0 and return WT_NOTFOUND, similarly to next. This call would be equivalent to calling WT_CURSOR::next followed by WT_CURSOR::get_raw_key_value.
The stub API would ideally be implemented at the cursor type for file:, with the corresponding plumbing from table: and layered: cursors, and it would include the corresponding Python bindings. We only need to support this function on the row store; all other cursor types (e.g., the column store, statistics) should return ENOTSUP.
As a part of this ticket, we should also define and increment a dedicated statistic for the new cursor function.
If any of this makes the scope of the ticket to be too big, we can split out some of this work into another ticket.
The test should also include basic functionality test in test/suite and/or a catch2 unit test, which at least ensures that (1) next_raw_key_value_batch returns at least one key-value pair if available, (2) has the appropriate return values, and (3) updates the statistics accordingly.