feat(panel): Add the "Report a broken page" view

[smalluban]

The PR adds the CTA for paused domains, which opens the "Report a broken page" in the panel.

• It looks like activeTab permission does not trigger a browser popup when the extension is updated. However, we can also try out the optional permission if it is better.
• We need to match operating systems between the extension and support form - I think we should update fields to follow extension logic - mac, win, ios, ipados,linux, etc... and version only as a separate field (currently we have windows_10 and other as os name)
• Copy is a draft version - needs review and improvements
• I tested the screenshot feature on Chrome, Firefox, and Safari on Mac and iOS, and it works as expected
• Open question about the link "Report a broken page" in the menu - should it also open the form in the panel or should it open the website as it does now?

WARNING: the PR logic is finished and it's connected to the real end-point. Please use npm start -- --staging when testing to avoid spaming the support channel.

[chrmod]

Screenshots for reference:

[chrmod]

Looks great so far!

[chrmod]

We should pass the product version via the form. Until it is supported by the website lets add it to the message.

Lets consider if we want to add also:

• list of detected activities (no urls)
• extension settings
• block list version (checksums)

[smalluban]

I had to miss it, I'll add the extension version via the subject. It might be easier to spot or filter out.

The message body has a limit of 5k characters. We can shorten it to 4k for a space of 1k for additional metadata. We can add a list of tracker IDs (from stats), extension settings are important from the privacy section only. The block list might be tricky as it requires all checksums of all lists, but I will try to generate them.

[smalluban]

• Updated copy from @mdsandu
• Added version, options, and trackers to the description
• Additional info when an error occurs

The PR is ready for final review for merging.

[smalluban]

There is a last open question - what about the link to report a broken page in the menu section of the panel? I am unsure if it should be changed, as the user might want to report "some" page - it does not have to be the one it is now... And if we change that, there will be no direct link to the form on the ghostery.com

[mdsandu]

pls post current screens to resolve the last issue. thanks

[smalluban]

Updated copy:

[github-actions]

Builds for commit defe976:

• ghostery-chromium-10.4.20-defe976
• ghostery-firefox-10.4.20-defe976

[Dimi-GE]

Screenshots from Zendesk:

[mdsandu]

@smalluban two suggested changes to cover your concern
same text in 2 locations clarifying (hopefully)

• on screen 1 add "If the issue persists or you’d like to report a different page as broken, please use the report form on ghostery.com" below "Include a screenshot of the current page" with a bit of spacing in between.

• on screen 2/fail screen: expand the red text to same message "If the issue persists or you’d like to report a different page as broken, please use the report form on ghostery.com"

let's see how this feels?