Process platform report metrics when extn is lagging

[lahsivjar]

The current extension will drop the platform.report logs if the platform report metrics are reported in an invocation that does not immediately succeed in the invocation generating the platform report. To prevent the logs from getting dropped the PR does the following changes:

1. Updates the lifecycle of the cached invocation data to be cleared on receiving platform.report metric for its corresponding request ID.
2. Query the cached invocation data instead of using the previous event and drop the log event if the prev event doesn't match the event's request ID.

Part of #334

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-01-12T08:51:15.772+0000

• Duration: 6 min 9 sec

Test stats 🧪

Test	Results
Failed	0
Passed	204
Skipped	2
Total	206

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[lahsivjar]

Apologies for the push after marking it ready for review. I realized there was an edge case when on shutdown there might be more than one platform.report pending. I have fixed this now.

[axw]

Looks good!

[lahsivjar]

/test