[SPARK-37445][INFRA][FOLLOWUP] Use hadoop3.2 profile instead of hadoo…

…p3 for the scheduled GA job for branch-3.2

### What changes were proposed in this pull request?

This PR fixes an issue that the scheduled GA job for `branch-3.2` fails.
SPARK-37445 (apache#34715), renamed the profile name `hadoop3.2` to `hadoop3` but It should be `hadoop3.2` for the scheduled build.
https://github.com/apache/spark/runs/4453894964?check_suite_focus=true

### Why are the changes needed?

To recover the job.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

The scheduled job itself.

Closes apache#34835 from sarutak/followup-SPARK-37445.

Authored-by: Kousuke Saruta <[email protected]>
Signed-off-by: Hyukjin Kwon <[email protected]>

.github/workflows/build_and_test.yml

@@ -69,7 +69,7 @@ jobs:
  echo '::set-output name=branch::branch-3.2'
  echo '::set-output name=type::scheduled'
  echo '::set-output name=envs::{"SCALA_PROFILE": "scala2.13"}'
- echo '::set-output name=hadoop::hadoop3'
+ echo '::set-output name=hadoop::hadoop3.2'
  elif [ "${{ github.event.schedule }}" = "0 10 * * *" ]; then
  echo '::set-output name=java::8'
  echo '::set-output name=branch::master'