feat: Sort kernel for RunArray

[askoa]

Which issue does this PR close?

Part of #3520

Rationale for this change

See issue description

What changes are included in this PR?

Built on top to yet to be merged PR #3681

• sort_run_to_indices for RunArray
• sort_run for RunArray
• Include sort run and sort run to indices in sort_kernel benchmark

Sorting run array to indices is very slow if the intention is to get output run array. The sorted indices are logical indices which has to be encoded back to run array. The function sort_run will rearrange runs based on sorted values and hence will be faster to get output run array.

How much faster is sort_run compared to sort_run_to_indices?

Below benchmark result shows sort_run produces the output run array using same time taken by sort_run_to_indices to produce indices.

sort primitive run to indices 2^12
                        time:   [11.023 µs 11.054 µs 11.096 µs]
Found 14 outliers among 100 measurements (14.00%)
  2 (2.00%) high mild
  12 (12.00%) high severe

sort primitive run to run 2^12
                        time:   [10.165 µs 10.267 µs 10.410 µs]
Found 12 outliers among 100 measurements (12.00%)
  6 (6.00%) high mild
  6 (6.00%) high severe

What's the catch?

The sort_run will only rearrange the runs and not re-encode them for efficiency. For e.g. an input RunArray { run_ends = [2,4,6,8], values = [1,2,1,2] } will result in output RunArray { run_ends = [2,4,6,8], values = [1,1,2,2] } and not RunArray { run_ends = [4,8], values = [1,2] }. The output of sort_run_to_indices can be used to re-encode the RunArray.

Are there any user-facing changes?

Users will get a new sort function for RunArray

[tustvold]

I intend to review this fully tomorrow morning

[askoa]

I just noticed a key issue in this code. So changing this to draft.

[tustvold]

Looks good to me, sorry for taking so long to review. Left some minor comments

[ursabot]

Benchmark runs are scheduled for baseline = e753dea and contender = ebe6f53. ebe6f53 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ursa-thinkcentre-m75q] ursa-thinkcentre-m75q
Buildkite builds:
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java