Flaky build failure in migrationConsole due to network hiccup when building

[peternied]

The build failure is because there was a network hiccup when the docker container assembly failed to download the kafka distribution - the external network call failed.

I proposal to pull the download of kafka and aws-msk-iam-auth out of the image building process, pulling them instead from gradles cache. Maybe there is a precedent for how another project accomplishes this?

Pro:

• Reused already downloaded artifacts from gradle build
• Removes potential source of flakiness from build
• Prevent version mismatches if latest != the version we depend on in the common dependencies

Con

• Effort to build it

> Could not build image: The command '/bin/sh -c wget -qO- https://archive.apache.org/dist/kafka/3.6.0/kafka_2.13-3.6.0.tgz | tar --transform 's!^[^/]*!kafka!' -xvz' returned a non-zero code: 2
> Task :TrafficCapture:dockerSolution:buildDockerImage_migrationConsole FAILED

opensearch-migrations/TrafficCapture/dockerSolution/src/main/docker/migrationConsole/Dockerfile

Lines 8 to 9 in 22d3f74

	RUN wget -qO- https://archive.apache.org/dist/kafka/3.6.0/kafka_2.13-3.6.0.tgz | tar --transform 's!^[^/]*!kafka!' -xvz
	RUN wget -O kafka/libs/msk-iam-auth.jar https://github.com/aws/aws-msk-iam-auth/releases/download/v2.0.3/aws-msk-iam-auth-2.0.3-all.jar

Originally posted by @peternied in #699 (comment)

[peternied]

Converted into Jira task https://opensearch.atlassian.net/browse/MIGRATIONS-1850