handle pekko deprecations

[bdoyle0182]

Description

handles deprecations going to pekko added in later akka 2.6 and pekko 1.1. changes are done such that there are no behavior changes.

The status code enum change is just in name, it still represents the same status code.

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.

[dgrove-oss]

lgtm