fix(core): stop recommending maxBytesInFlight

[WilliamK112]

What changed

Removes the AutoTuner recommendation for spark.rapids.shuffle.multiThreaded.maxBytesInFlight.

Why

Fixes #1710. The issue notes that this recommendation should be removed because it does not use metrics to make the decision, and the issue discussion has maintainer confirmation to remove it.

Details

• Removed the MAX_BYTES_IN_FLIGHT tuning config and recommendation path from AutoTuner.
• Simplified memory calculation to return only MemorySettings instead of carrying a maxBytesInFlight recommendation flag.
• Updated profiling and qualification expected outputs to remove the recommended Spark property and reflect the reclaimed memory in pinned pool sizing.
• Kept the tuning table Spark property entry so explicit user configs for that Spark key can still be recognized by the tuning metadata.

Validation

• git diff --check
• cd core && JAVA_HOME=$(/usr/libexec/java_home -v 17) mvn -DwildcardSuites=com.nvidia.spark.rapids.tool.tuning.ProfilingAutoTunerSuiteV2 test
• In a temporary worktree without spaces in the path:
  • cd core && JAVA_HOME=$(/usr/libexec/java_home -v 17) mvn -DwildcardSuites=com.nvidia.spark.rapids.tool.tuning.QualificationAutoTunerSuite test
  • cd core && JAVA_HOME=$(/usr/libexec/java_home -v 17) mvn -DwildcardSuites=com.nvidia.spark.rapids.tool.tuning.ProfilingAutoTunerSuite test

Note: the Qualification and legacy Profiling suites hit path-related failures from the local workspace path (New project) but passed from the temporary /tmp worktree with the same patch applied.