Remove preserve_order feature from serde_json dependency (#2095)

[tustvold]

Which issue does this PR close?

Closes #2095

Rationale for this change

See #2095 and #1882

What changes are included in this PR?

Disables the serde_json, preserve_order feature

Are there any user-facing changes?

Potentially, although as noted by @nevi-me #1882 (comment) it would likely be incorrect for a user to be relying on this behaviour anyway.

[alamb]

Can we remove indexmap while we are at it?

[alamb]

Also, can we make the test change suggested by @nevi-me in #1882 (comment) ?

[tustvold]

I think I would rather keep this change smaller, and we can remove indexmap, etc... as a follow up?

[alamb]

Let's do it . Thanks @tustvold

[ursabot]

Benchmark runs are scheduled for baseline = 619be77 and contender = 2541e2c. 2541e2c 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