Check for integer overflow when narrowing Query skip

[anjeongkyun]

• You have read the Spring Data contribution guidelines.
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.
• You added yourself as author in the headers of the classes you touched.

Motivation

Query.skip takes a long and Pageable.getOffset() returns a long, but the driver and the wire protocol take an int. Three places narrowed with a plain cast:

// QueryOperations
if (query.getSkip() > 0) {
    options.skip((int) query.getSkip());
}

// MongoTemplate
cursorToUse = cursorToUse.skip((int) skip);

// ReactiveMongoTemplate
findPublisherToUse = findPublisherToUse.skip((int) skip);

The > 0 check passes for a large skip, and the cast then wraps it to a negative that goes straight to the driver. PageRequest.of(500_000, 5_000) carries an offset of 2,500,000,000, which arrives as -1,794,967,296, and SliceUtils.limitResult feeds exactly that into Query.skip.

Change

The three sites share a check that reports the offending value rather than wrapping it. skip values inside the range behave as before.

I put the helper on QueryOperations since two of the three callers already reach for it; say the word if you would rather have it somewhere else, or inline at each site.

QueryOperationsUnitTests, MongoTemplateUnitTests and ReactiveMongoTemplateUnitTests pass (356 tests). The new test fails without the change.

There is no ticket for this one, happy to add the GH- reference to the tests if you open one.