DevTools tab for debugging

[taneltm]

Adds the "Web eID" tab to the browser's DevTools.

Features:

• Event history between the website, extension and native application.
• Extension's internal log messages.
• Option to override extension settings, without needing to compile the extension yourself.
• Option to allow the http://localhost origin when authenticating and signing

The developer tool is disabled by default and needs to be enabled before it can be used.

Firefox

1. Open [Menu -> Settings -> Extensions and themes]
   or navigate to the address about:addons
2. Open the Web eID extension details
3. Open the "Permissions" tab
4. Toggle "Extend developer tools to access your data in open tabs"

Chrome

1. Open [Settings -> Extensions]
   or navigate to the address chrome://extensions/
2. Open the Web eID extension details
3. Open "Extension options"
4. Toggle "Enable developer tools"

Screenshots:
Viewing event sequence and the event objects:

Viewing the extension's internal log messages:

Overriding the extension settings:

Resolves WE2-967
Resolves #40

[mrts]

Do the Firefox consent pages end up in Chrome as well with this?

[taneltm]

Yes, installed.html+js ends up in the chrome build, but aren't used. This should be fixed.

[svenzik]

Usability suggestions from chrome testing:

Events tab: Reloading the page does not clear the events. There is no button for clearing them (also tested that clearing log does not clear events).

Log tab: Even though there is clear button, the chrome console, network tools etc is cleared each time page is reloaded. I suggest we follow that principle.

Please also consider, If we clear the log tab on reload, then chrome console has a setting preserve log. Should we have similar setting?

[taneltm]

Hi @svenzik!

Good point about not having the ability to clear the events! I'll add it as soon as I have a moment.

However, not clearing the logs on page reload was intentional.
When working on single-page apps, it does make sense to clear the logs on reload, but on multi-page websites where, after auth or sign, you are navigated to another page, and then it would be good to keep the logs.
I would like to keep the current behaviour as default and maybe add a "clear on reload" option. That might be a tiny bit annoying for the SPA developers, but I think it's less confusing for others.
I'll discuss this topic with the team next week before making any decisions on this. I appreciate your feedback about it and will keep it in mind - maybe it would be good to follow the browser DevTools pattern... 🤔

Thank you for taking the time to test it!