BIGTOP-3682: Failed to build sqoop for Debian 11 on Arm64

[guyuqi]

Failed to build: Cannot run program "python" No such file or directory.

Description of PR

This PR is to fix build issue of sqoop for Debian 11 on Arm64, which is described in BIGTOP-3682.

How was this patch tested?

Successfully build on Arm64 Debian 11.

For code changes:

• Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'BIGTOP-3638. Your PR title ...')?
• Make sure that newly added files do not have any licensing issues. When in doubt refer to https://www.apache.org/licenses/

[sekikn]

@guyuqi I think it's already been resolved with the latest Debian 11 image for ARM64. (I've just rebuilt it just before :)

[ec2-user@ip-172-31-28-215 bigtop]$ facter architecture
aarch64
[ec2-user@ip-172-31-28-215 bigtop]$ ./gradlew allclean sqoop-pkg-ind -POS=debian-11

...

Unable to find image 'bigtop/slaves:trunk-debian-11-aarch64' locally
trunk-debian-11-aarch64: Pulling from bigtop/slaves

...

Digest: sha256:12a27bd8d63a7e9d61969f13594c28eab91a5c1ce3654386e2576a0ecdb84ed6
Status: Downloaded newer image for bigtop/slaves:trunk-debian-11-aarch64

...

> Task :sqoop-pkg
Caching disabled for task ':sqoop-pkg' because:
  Build cache is disabled
Task ':sqoop-pkg' is not up-to-date because:
  Task has not declared any outputs despite executing actions.
:sqoop-pkg (Thread[Execution worker for ':',5,main]) completed. Took 0.001 secs.

BUILD SUCCESSFUL in 11m 47s

Is this sufficient for building Sqoop on ARM64? I personally think that linking python in sqoop/do-component-build is not so good, because it changes global environment depending on if building Sqoop or not.

[guyuqi]

It makes sense. Thanks, @sekikn