refactor: remove kind and order args to sorting protocols

[agoose77]

The sort and argsort internal Content protocols don't actually use the kind or order arguments. Awkward instead uses stable to determine the sorting algorithm used. This PR removes those unused arguments.

[codecov]

Codecov Report

Merging #2090 (524f1a4) into main (6efa287) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files

Impacted Files	Coverage Δ
src/awkward/contents/content.py	73.13% <ø> (ø)
src/awkward/_do.py	84.30% <100.00%> (ø)
src/awkward/contents/bitmaskedarray.py	68.02% <100.00%> (ø)
src/awkward/contents/bytemaskedarray.py	88.80% <100.00%> (ø)
src/awkward/contents/emptyarray.py	72.22% <100.00%> (ø)
src/awkward/contents/indexedarray.py	77.66% <100.00%> (ø)
src/awkward/contents/indexedoptionarray.py	88.67% <100.00%> (ø)
src/awkward/contents/listarray.py	90.08% <100.00%> (ø)
src/awkward/contents/listoffsetarray.py	80.11% <100.00%> (ø)
src/awkward/contents/numpyarray.py	91.19% <100.00%> (ø)
... and 4 more

[agoose77]

I've requested from @jpivarski too, because his comments on #2089 suggest that we might want to redefine our sorting API arguments.

[jpivarski]

This is related to, but independent of, #2112. This argument list is a relic of when ak.sort's arguments were more different from np.sort than they are now.

[jpivarski]

I'll be merging it without an explicit approval from @ianna. We were talking about the sort arguments today, and this is a detail of what we had agreed to.