Scope a solution ✅

Given that most steps are already available, this will cover the steps that aren't avaialble

Then: lcp image markup is not written to LL format
And: ATF image markup is not written to LL format

To implement this, we should have another function in lcp-beacon-script.ts to check for lazyloaded class in lcp/atf images. We can modify lcp image should have fetchpriority step and make the lcp images available outside the function scope.

Create a new step to install and activate imagify plugin here

Estimate the effort ✅
[S]

LGTM...

Update as per https://docs.google.com/spreadsheets/d/1YpkRpc_PkcszOezpkIooWC6hIWnkIWnXITvoHNjEjIo/edit?gid=0#gid=0 , we can split scenario2 into 2 scenarios
scenario A: Should exclude LCP/ATF from LL if display next-gen is enabled before lcp
Given: Imagify is enabled and display next-gen is enabled
And: page with images having next-gen images is visited
And: LL is enabled at WPR
When: clear cache
And revisit the page
Then: lcp/ATF aren't Lazyloaded in source

scenario B: Should exclude LCP/ATF from LL if display next-gen is enabled after lcp
Given: Imagify is enabled and display next-gen is disabled
And: page with images having next-gen images is visited
And: LL is enabled at WPR
When: clear cache
And: Enable display next gen picture at imagify
And revisit the page
Then: lcp/ATF aren't Lazyloaded in source

test page can be: https://e2e.rocketlabsqa.ovh/lcp_with_imagify/

Moving it in Blocked until next cooldown as it's been a while we've be circling around with this issue.