Avoid redundant whitespace scan in json.loads() for documents without surrounding whitespace

Decoding a JSON document with json.loads() runs a whitespace-skipping regular expression at the start and end of the document through the pure-Python decode() wrapper, on every call, before and after the C scanner does the actual parsing. The overwhelming majority of documents have no leading or trailing whitespace, so both matches scan zero characters yet still pay for the call and the match-object allocation. For the small documents that dominate real traffic, that fixed overhead is a meaningful fraction of the total decode time.

Skipping the leading match when the document does not begin with whitespace, and the trailing match when the parse already consumed the whole string, removes that overhead from the common case. On a tiny document it is roughly 1.5x faster; documents that do have surrounding whitespace keep the original behavior, and large documents are unaffected.

This overlaps with the broader rewrite proposed in gh-117397; it is filed separately so the small, self-contained version can be evaluated on its own.

Linked PRs

• gh-150861

Start at json.loads() and its pure-Python decode() wrapper, then compare the whitespace handling with the C scanner described in the issue and the broader rewrite in gh-117397. Done means documents without surrounding whitespace avoid redundant scans while documents with whitespace retain their behavior; gh-150861 indicates work is already underway.