[Variant] Move JSON related functionality to different crate.

[harshmotw-db]

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

Variant is not inherently tied to JSON and dealing with Variants should not have additional dependencies due to JSON interoperability. The JSON related functionality - variant_to_json and json_to_variant should be separated into a different crate (maybe parquet-variant-json) so it is easier to manage their dependencies.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

https://github.com/apache/arrow-rs/pull/7783/files/c41af4e89b46b7c512b199f0b605395c1bd09227#r2170069713

[alamb]

Here is a proposd PR to fix this:

• [Variant] Move JSON related functionality to different crate. #7800

[harshmotw-db]

@alamb I think the link is to this issue?

[alamb]

@alamb I think the link is to this issue?

Sorry -- here is the PR:

• [Variant] Introduce parquet-variant-json crate #7862

[alamb]

label_issue.py automatically added labels {'parquet'} from #7862