fix: [branch-1.1] match SPARK-58821 and SPARK-60118 in sequence and string to decimal cast (#7171) - #7266

…mal cast (apache#7171)

* fix: match SPARK-58821 and SPARK-60118 in sequence and string to decimal cast

Spark 4.0.5, 4.1.4 and 4.2.1, now in release candidates (4.0.5-rc3,
4.1.4-rc4 and 4.2.1-rc3), change two results that Comet reproduces
natively:

- SPARK-58821: when stop - start overflows a long but the length is small,
  sequence() returns the elements, where earlier releases raise
  INTERNAL_ERROR("Unreachable code reached."). A new native variant,
  spark_sequence_recomputed, does the same, and
  CometSequence.nativeFunction picks it on those releases.
- SPARK-60118: casting a string to decimal no longer applies the
  integral-digit limit to zero, so a zero with a large exponent ("0e79")
  casts to 0 instead of NULL (or NUMERIC_OUT_OF_SUPPORTED_RANGE under ANSI).
  CometCast sets a new Cast proto field, decimal_zero_any_exponent, and
  parse_string_to_decimal skips the zero limit when it is set.

SparkFixes holds the version checks. The internal-error case in
sequence.sql moves to CometArrayExpressionSuite, because SQL file version
directives compare only major.minor.

* docs: describe SPARK-60119 and the version-number caveat, and share one version table

Review follow-up.

- SPARK-60119, which is in the same release candidates, makes Spark return
  0.00 for a string far below the target scale's ulp, as the native cast
  already does. The cast audit entry and the string.rs comments now say
  that apache#6966's positive-scale case applies only before 4.0.5, 4.1.4 and
  4.2.1, and that its negative-scale case still differs on them.
- The cast compatibility page and CometSequence's compatibility notes say
  that Comet chooses by the Spark version number, and what a vendor build
  that reports an older version but includes SPARK-60118 or SPARK-58821
  returns, as floating-point.md does for SPARK-59602.
- recomputed_length_after_overflow keeps only the new element checks.
  length_limit_and_overflow_edges and the length grid already cover the
  internal error and both variants' limit errors.
- SparkFixesSuite holds one version table for both fixes and
  CometSequence.nativeFunction, replacing the near-identical tables in
  CometArrayExpressionSuite and CometNativeCastSuite, which keep their
  convert checks. It is listed in both PR build workflows.

* fix: follow released Spark for '0e2147483647', and check Spark's error in the sequence test

Review follow-up.

- On the released path, parse_string_to_decimal counts a zero's integral
  digits as 1 - scale with a wrapping i32 subtraction, as Spark's int
  arithmetic does, so '0e2147483647' casts to 0 there. The zero test covers
  it, and two inputs whose counts don't wrap.
- The sequence overflow test's released-Spark branch uses checkSparkError,
  which checks Spark's INTERNAL_ERROR, exception class and SQLSTATE rather
  than the message.
- The cast audit entry describes SPARK-60118's long digit count: released
  Spark throws for '1e2147483647' and similar strings, the fixed releases
  return NULL or raise NUMERIC_OUT_OF_SUPPORTED_RANGE, and the native cast's
  ANSI error is apache#7188.
- SparkFixes' scaladoc names the two fixes it covers and points to the
  other version checks.

Adapted for branch-1.1, which predates parts of main next to apache#7171's lines:

- sequence.rs: branch-1.1's kernel takes the start, stop and step arrays
  and a conversion closure, and its sequence_length flags the overflow
  itself, so the OverflowedLength choice is threaded through that code.
  The new test also checks that a length over the limit is still an
  error with spark_sequence_recomputed, which main's length grid covers.
- string.rs: the zero_any_exponent change and its test. The SPARK-60119
  comment rewording is dropped, since branch-1.1 doesn't have the
  scale-adjustment comments it edits.
- planner.rs: branch-1.1's SparkCastOptions::new_with_version still takes
  allow_incompat.
- The contributor-guide audit entries are dropped, since that guide isn't
  published from release branches and they describe main's code.
  SparkFixes' scaladoc doesn't mention ArraySetSupport.normalizesFloats,
  which branch-1.1 doesn't have.
- Import lists keep branch-1.1's names plus the ones apache#7171 adds.

(cherry picked from commit 1dec4c0)