Upgrading library versions to incorporate the latest Log4j fix

These updates apply version 2.17, addressing CVE-2021-45105

(cherry picked from commit 894713a0)

Conflicts:
	pom.xml
	provider/notification-aws/pom.xml
	provider/notification-azure/pom.xml
	provider/notification-gcp/pom.xml
	provider/notification-ibm/pom.xml
9 jobs for cherry-pick-update-log4j-2.17 in 7 minutes and 25 seconds (queued for 7 seconds)
Name Stage Failure
failed
deprecated-pipeline-include .Pre
Removing helm.tgz
Removing linux-amd64/

Skipping Git submodules setup
Executing "step_script" stage of the job script
$ echo "$DEPRECATED_MSG"
The FOSSA scanner now supports different build environments, which should be specified directly. Consider using fossa-maven.yml instead.
$ /bin/false
ERROR: Job failed: exit code 1
failed
deprecated-aws-include .Pre

Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:c059bfaa849c4d8e4aecaeb3a10c2d9b3d85f5165c66ad3a4d937758128c4d18 for alpine:latest with digest alpine@sha256:21a3deaa0d32a8057914f36584b5288d2e5ecc984380bc0118285c70fa8c9300 ...
$ echo "$DEPRECATED_MSG"
The AWS includes now support different build environments, which should be specified directly. Consider using: aws-global.yml, and either aws-maven.yml or aws-python.yml
$ /bin/false
Cleaning up file based variables
ERROR: Job failed: exit code 1