HADOOP-19398: Upgrade Dockerfile base to jammy

[YanivKunda]

Description of PR

Upgrade the base image of the Ubuntu Dockerfiles used for CI and local development.

How was this patch tested?

1. Created and started the build env: ./start-build-env.sh
2. Built native profile (within the container): mvn clean install -Pnative -DskipTests

For code changes:

• Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
• Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
• If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

[hadoop-yetus]

💔 -1 overall

Vote	Subsystem	Runtime	Logfile	Comment
+0 🆗	reexec	17m 53s		Docker mode activated.
			_ Prechecks _
+1 💚	dupname	0m 0s		No case conflicting files found.
+0 🆗	codespell	0m 0s		codespell was not available.
+0 🆗	detsecrets	0m 0s		detect-secrets was not available.
+0 🆗	shellcheck	0m 0s		Shellcheck was not available.
+0 🆗	shelldocs	0m 0s		Shelldocs was not available.
+0 🆗	hadolint	0m 0s		hadolint was not available.
+0 🆗	jsonlint	0m 0s		jsonlint was not available.
+1 💚	@author	0m 0s		The patch does not contain any @author tags.
-1 ❌	test4tests	0m 0s		The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.
			_ trunk Compile Tests _
+0 🆗	mvndep	5m 47s		Maven dependency ordering for branch
-1 ❌	mvninstall	18m 55s	/branch-mvninstall-root.txt	root in trunk failed.
-1 ❌	compile	6m 44s	/branch-compile-root.txt	root in trunk failed.
-1 ❌	mvnsite	2m 21s	/branch-mvnsite-root.txt	root in trunk failed.
+1 💚	shadedclient	53m 8s		branch has no errors when building and testing our client artifacts.
			_ Patch Compile Tests _
+0 🆗	mvndep	0m 21s		Maven dependency ordering for patch
-1 ❌	mvninstall	17m 50s	/patch-mvninstall-root.txt	root in the patch failed.
-1 ❌	compile	1m 28s	/patch-compile-root.txt	root in the patch failed.
-1 ❌	cc	1m 28s	/patch-compile-root.txt	root in the patch failed.
-1 ❌	javac	1m 28s	/patch-compile-root.txt	root in the patch failed.
+1 💚	blanks	0m 0s		The patch has no blanks issues.
-1 ❌	mvnsite	2m 32s	/patch-mvnsite-root.txt	root in the patch failed.
+1 💚	shadedclient	22m 39s		patch has no errors when building and testing our client artifacts.
			_ Other Tests _
-1 ❌	unit	293m 50s	/patch-unit-root.txt	root in the patch failed.
+1 💚	asflicense	0m 47s		The patch does not generate ASF License warnings.
		409m 13s

Reason	Tests
Failed junit tests	hadoop.hdfs.TestDecommissionWithBackoffMonitor
	hadoop.hdfs.TestDecommission

Subsystem	Report/Notes
Docker	ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7320/1/artifact/out/Dockerfile
GITHUB PR	#7320
Optional Tests	dupname asflicense codespell detsecrets shellcheck shelldocs hadolint mvnsite unit jsonlint compile cc javac
uname	Linux bb5300e8b22e 5.15.0-130-generic #140-Ubuntu SMP Wed Dec 18 17:59:53 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Build tool	maven
Personality	dev-support/bin/hadoop.sh
git revision	trunk / 49bf29f
Default Java	Red Hat, Inc.-1.8.0_412-b08
Test Results	https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7320/1/testReport/
Max. process+thread count	3780 (vs. ulimit of 5500)
modules	C: hadoop-hdfs-project/hadoop-hdfs-native-client . U: .
Console output	https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7320/1/console
versions	git=2.9.5 maven=3.6.3
Powered by	Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

[slfan1989]

@YanivKunda Thank you for the contribution! It can't pass the compilation successfully. We still need to continue improving it. Looking forward to the completion of this PR.

[YanivKunda]

@slfan1989 It seems to fail on grpc-protoc generation on centos-7 -
I think the only change that can affect it is the boost upgrade (1.72 -> 1.74), but I'm actually not much of a C++/native expert.
But the question what are the different supported platforms used for?
I know the Ubuntu ones is used for CI and for local dev environment, but what are centos-7/centos-8/debian-10 used for?

Also, centos-7 is EOL for more than 6 months now:
https://www.redhat.com/en/topics/linux/centos-linux-eol
In fact, centos in general is discontinued (principally replaced by centos-stream).
In addition, debian-10 LTS ended around the same time.

Should supporting these be pursued, or are they are going to be gone any time soon?