Add waitForEvent tasks to release notes

[ankur22]

What?

Update the next release notes with links to the PRs that have fixed and refactored code to get waitForEvent to work.

Why?

To update the release notes for the next release.

Checklist

• I have performed a self-review of my code.
• I have added tests for my changes.
• I have run linter locally (make lint) and all checks pass.
• I have run tests locally (make tests) and all tests pass.
• I have commented on my code, particularly in hard-to-understand areas.

Related PR(s)/Issue(s)

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (release-notes-v0.48.0@af4dd63). Click here to learn what that means.

❗ Current head 5fa24ab differs from pull request most recent head 09ebc51. Consider uploading reports for the commit 09ebc51 to get more accurate results

Additional details and impacted files

@@                   Coverage Diff                    @@
##             release-notes-v0.48.0    #3413   +/-   ##
========================================================
  Coverage                         ?   73.11%           
========================================================
  Files                            ?      258           
  Lines                            ?    19650           
  Branches                         ?        0           
========================================================
  Hits                             ?    14367           
  Misses                           ?     4401           
  Partials                         ?      882           

Flag	Coverage Δ
ubuntu	73.05% <0.00%> (?)
windows	72.95% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ka3de]

My understanding is that grafana/xk6-browser#1069 is not specifically related with waitForEvent, as it also refactors the usage of TaskQueue for Page.on. Should we remove it from here and instead add an entry for it under Maintenance and internal improvements section?

[ankur22]

Yeah, good point, it does include quite a bit of refactoring to move the taskqueue out of the common package and into the mapping layer. The main motivation (initially) for this PR though was due to the issue of not working with the taskqueue when using the predicate function for waitForEvent, i.e. without this change waitForEvent wouldn't work. Happy to move it to Maintenance and internal improvements though if you still think it should, WDYT?

[ka3de]

To me it feels moving the TaskQueue to the mapping layer is a separate task. But no strong opinion.

[ankur22]

Ok, happy with that change added it to a fixup: ef92133

[ka3de]

How specific should we be with these internal refactors? To be honest I'm never sure of what should be the level of detail in these cases. Considering that this is a completely internal change, I don't disagree with the current text, but I wonder if it should be more specific such as "Internal refactor to move Goja's TaskQueue away from core implementation" (or similar).

Since you are a reviewer for this also, any thoughts @oleiade ?

[ankur22]

Mind if i merge this and we can open a new issue for this if we need?

[ka3de]

LGTM.