[FEA] enable from_json and json scan by default

[revans2]

Is your feature request related to a problem? Please describe.
We will not be perfect in everything that we do, but we should be close enough that that we can enable most of from_json and json scan by default. There are still outstanding issues that prevent us from enabling all config options and all data types in all versions of Spark. There are also some odd corner cases that we need to at least document how we are different. We should also provide some configs to enable and disable data types individually.

Things that must be fixed before we can enable from_json and json scan by default

• [BUG] JsonToStructs fails to parse all empty dicts and invalid lines #10483 (I think this is done but I need to go over the tests again to be sure that it is)
• [BUG] from_json does not support input with \n in it. #10489 (I think this is done but I need to go over the tests again to be sure that it is)
• [BUG] cudf::read_json incorrectly parses invalid JSON string rapidsai/cudf#16999
• [BUG] cudf::io::json::detail::normalize_single_quotes outputs incorrect result when the input has \n character rapidsai/cudf#17261

Types that we do not support by default:

• Top level arrays are not supported
• Top level Maps should still be off by default
• Dates
  • [FEA] Support parsing dates and timestamps with timezone IDs in the string #6846
  • [BUG] refine timestamp for JsonToStructs and ScanJson #10535
  • [BUG] For from_json and scan json parsing a quoted string timestamp for Spark 3.2 is wrong #11391
  • [FEA] Support reading JSON numeric values as timestamps and dates #4940
  • [FEA][JSON] Support parsing single numbers in strings as dates in from_json #9664
  • [FEA] Add support for constant timestamp values such as "now" in from_json (Spark 3.1.x only) #9724
• Timestamps
  • [FEA] Support parsing dates and timestamps with timezone IDs in the string #6846
  • [BUG] refine timestamp for JsonToStructs and ScanJson #10535
  • [BUG] For from_json and scan json parsing a quoted string timestamp for Spark 3.2 is wrong #11391
  • [FEA] Support reading JSON numeric values as timestamps and dates #4940
  • [FEA][JSON] Support parsing single numbers in strings as dates in from_json #9664
  • [FEA] Add support for constant timestamp values such as "now" in from_json (Spark 3.1.x only) #9724

Configs that we do not support by default:

• non-UTC time zones if a timestamp or date type is present. ([BUG] time zone checks for from_json are too broad and do not follow JsonScan #10453)
• non-default timestampFormat/dateFormat if a timestamp or date type is present ([BUG] setting timestampFormat/dateFormat for JsonToStructs appears to fall back too often and also not often enough #10485)

Things that must be documented as corner cases:

• Numbers are not normalized like they are in Spark or even like they are in get_json_object when read as a string
  • [FEA] JSON number normalization when returned as a string rapidsai/cudf#15318
  • [BUG] JsonToStructs and ScanJson does not normalize non quoted strings when read as strings #10574
• allowNonNumericNumbers matches later versions of Spark when validating results ([BUG] On versions of Spark prior to 3.3.0 we produced incorrect JSON results for allowNonNumericNumbers #10493)
• A double " inside a single quoted string is handled correctly by the RAPIDS Accelerator, but incorrectly by versions of Spark before 3.3.0 ([BUG] ScanJson on versions prior to 3.3.0 where a double quote " appears in a single quoted string produce the wrong answer on CPU #10495)
• The RAPIDS Accelerator does not handle parsing non-arabic number in quoted strings ([BUG] Decimal parses non-arabic numbers #10532)
• non-top level arrays with numeric values that overflow produce different results ([FEA] JsonToStructs and ScanJson should invalidate the entire array on overflow #10573, [BUG] JSON Scan and JsonToStruct should invalidate an array on out of bounds #11491)
• non-top level structs/objects with numeric values that overflow produce different results on Spark 3.4.1 and below ([BUG] JsonToStructs does not match parsing invalid structs on Spark 3.4.1 and below #10588)
• duplicate named values in an array are not handled the same as spark ([BUG] fix issues with repeated JSON columns #11361)
• Spark 3.2.X will parse quoted integers, but the RPAIDS accelerator follows later versions of Spark ([BUG] For from_json and scan json parsing a quoted string int for Spark 3.2 is wrong #11390, https://issues.apache.org/jira/browse/SPARK-38060)
• [BUG] from_json and scan json do not replace \u escaped chars in nested data returned as a string. #11632