Fix Databricks 13.3 BroadcastHashJoin using executor side broadcast fed by ColumnarToRow [Databricks]

[tgravescs]

fixes #10165

Here the issue is that Databricks supports a special executor side broadcast in BroadcastHashJoin and in this case the BroadcastHashJoin ended up being on the CPU. The BroadcastHashJoin can't be fed by a ColumnarToRow. It expects to be fed by an exchange that specifically handles going to a single partition.
There is a similar issue in Databricks 12.2 that we fixed by inserting an extra GpuColumnarToRow and then an Exchange. I use similar logic here to fix this and filed a followup to investigate the performance of now having 2 exchanges (#10229).

The beginning plan looks like:

Caused by: org.apache.spark.SparkException: Unexpected build plan for Executor Side Broadcast Join: 
ColumnarToRow
+- AQEShuffleRead ebj
   +- ShuffleQueryStage 132, Statistics(sizeInBytes=7.8 MiB, rowCount=2.74E+5, ColumnStat: N/A, isRuntime=true)
      +- GpuColumnarExchange gpuhashpartitioning(cast(user_id#83458 as int), 200), ENSURE_REQUIREMENTS, [plan_id=394739]
         +- GpuProject [gpucoalesce(user_id#84619, cast(user_id#84639 as string)) AS user_id#83458, if ((gpucoalesce(is_deleted#84640, true) AND NOT (cast(user_id#84619 as int) = 117563))) gdpr-deleted else gpucoalesce(email_address#84631, email_address#84646) AS email_address#83462]
            +- GpuRowToColumnar targetsize(268435456)

After this fix the plan looks like:

 +- Exchange (SinglePartition, EXECUTOR_BROADCAST)
             *     +- GpuColumnarToRow
             *         +- GpuShuffleCoalesce
             *             +- ShuffleQueryStage
             *                 +- GpuColumnarExchange

Added an integration test for databricks. The test throws an exception without the fix and then passes with the fix. This new logic only occurs on Databricks 13.3 and the parameters to AQEShuffleReadExec changed between 12.2 and 13.3 so the shim code went into a specific Databricks 13.3 file.

[tgravescs]

Note, not kicking the build because I know the databricks one is currently broken from other issues

[sameerz]

build

[revans2]

But I really would like more eyes on it than just mine.