fix: treat resume as start if sessions lost, trigger resume if needed

[sidvishnoi]

Context

Closes #841
Closes #871
More context: #871 (comment)

Changes proposed in this pull request

• Make ResumeMonetizationPayload to be same as StartMonetizationPayload
• When resume is called and background doesn't have sessions, use that payload to trigger a "start monetization". This addresses back-forward navigation sessions cleared issue.
• To address resume on sleep-clearing-all-sessions-in-background (here we don't have a payload we can trigger start from), pass REQUEST_RESUME_MONETIZATION message to content script to call resume in content, which will trigger the start.
• Trigger this resume on in background.start().

Testing

See #871 (comment) for how to reproduce. The bf-cache one is covered by E2E tests, but sleep one requires manual testing. I've tested following scenarios (with computer sent to sleep around 60-70 times 😆):

• Press Win+X U S to put computer to sleep (triggers window focus lose typically), Click start menu -> power -> sleep (doesn't trigger window focus lose typically)
• Keep monetized open when sending computer to sleep; keep window minimized when sending to sleep
• Keep a non-monetized tab active (window in view/minimized both cases)

[github-actions]

Extension builds preview

Name	Link
Latest commit	76c09d7
Latest job logs	Run #13495863162
	Download
	Download

[sidvishnoi]

test-e2e

[sidvishnoi]

test-e2e

[DarianM]

fix was tested on Windows for Firefox/Chrome/Edge:

• Win X U S with active tab monetized on minimized
• keeping monetized browser tab open when sending computer to sleep
• keeping monetized browser tab minimized when sending to sleep
• have a non-monetized tab focused, send to sleep, then focus monetized tab back (+ case lose focus with Win X U S)
• have a non-monetized tab minimized, then focus monetized tab back (+ case lose focus with Win X U S)

also this is a fix for #841 on Firefox/Chrome/Edge