Cache configuration with Edge hit (resolves #367)

[kevinlind]

Description

Cache the Edge configuration with the queued data entity instead of retrieving the configuration when the hit is processed. This update preserves the previous EdgeHitProcessor workflow to handle cases where queued data entities without a configuration are present after upgrading to this newer version.

• Edge extension will now bundle the edge configuration in the EdgeDataEntity when adding entity to queue.
• EdgeHitProcessor now reads the edge configuration from the EdgeDataEntity instead of getting it from the current Configuration shared state.
• EdgeHitProcess continues to use old workflow of validating against readyForEvent and reading the Configuration shared state if the current data entity contains an empty configuration.

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[emdobrin]

minor comment on docs, looks good

[emdobrin]

doesn't seem to return nil 🤓