Apache Pekko Migration

[bdoyle0182]

Apache Pekko Migration

Description

This PR migrates the Apache Openwhisk project to the latest versions of libraries from Apache Pekko. All references to Lightbend Akka in the repo have been removed.

Changes

• Updated from Akka 2.6 to latest Pekko. All references to Akka in the repo are gone and all links to documentation in the repo have been updated to the matching Pekko equivalent.

1. pekko-kryo-serialization 1.3.0. This introduces a breaking change to existing cluster going to Kryo5 from Kryo4
2. pekko core 1.1.5
3. pekko-kafka 1.1.0
4. pekko-http 1.1.0
5. pekko-management 1.1.1
6. pekko grpc 1.1.1. This goes through Akka grpc 2.x breaking change.

• All remaining transitive dependency cve's have been remediated.

• Updated kafka-clients / embedded-kafka to 3.9.1 from 2.8.2 as required by Pekko (verified can run standalone openwhisk)

• Updated zookeeper to 3.9.3

• Updated netty to latest 4.1.x and gRPC core of 1.75.0. Pinned gRPC dependencies so we can keep required parity across dependencies.

• Updated scalatest to 3.2.14 from 3.0.8 as required by Pekko.

• The s3 pekko connector had some breaking changes from what we were on. New configs were required, I set them such that the behavior remains unchanged from what was there.

• Updated ansible deploy commands of core components to output logs on error of healthcheck for easier debugging in CI jobs.

• Disabled xFatalWarn on compile to ignore deprecation warnings in this PR. Small amount of deprecations will be handled in follow up PR turning xFatalWarn back on.

Related issue and scope

• I opened an issue to propose and discuss this change (#????)

My changes affect the following components

• API
• Controller
• Message Bus (e.g., Kafka)
• Loadbalancer
• Scheduler
• Invoker
• Intrinsic actions (e.g., sequences, conductors)
• Data stores (e.g., CouchDB)
• Tests
• Deployment
• CLI
• General tooling
• Documentation

Types of changes

• Bug fix (generally a non-breaking change which closes an issue).
• Enhancement or new feature (adds new functionality).
• Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

• I signed an Apache CLA.
• I reviewed the style guides and followed the recommendations (Travis CI will check :).
• I added tests to cover my changes.
• My changes require further changes to the documentation.
• I updated the documentation where necessary.

[bdoyle0182]

I have completed a self review pass of the entire diff and LGTM