Improve browser experience

[blackdevelopa]

Development & PR Process

1. Follow MetaMask Mobile Coding Standards
2. Add release-xx label to identify the PR slated for a upcoming release (will be used in release discussion)
3. Add needs-dev-review label when work is completed
4. Add needs-qa label when dev review is completed
5. Add QA Passed label when QA has signed off

Description

Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions,
1. What is the reason for the change?
2. What is the improvement/solution?

Screenshots/Recordings

If applicable, add screenshots and/or recordings to visualize the before and after of your change

Issue

Progresses
#458
#354

Checklist

• There is a related GitHub issue
• Tests are included if applicable
• Any added code is fully documented

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[Cal-L]

Left some comments. You can ignore the areas where I commented that I tagged. It's just a way for me to identify the areas of code that changed. Btw, it looks like there are a bunch of changes that you didn't actually touch. If you have the chance, I'd recommend reapplying the changes that you made and then re-patching to see if you still get all of the diffs.

[Cal-L]

LGTM!

[cortisiko]

@Cal-L @blackdevelopa @NicholasEllul This PR does what it was set out to do. I went ahead and did the browser regression and reported my findings here.

[blackdevelopa]

@cortisiko I have now updated the cirt app description here

[cortisiko]

After discussing the above with @blackdevelopa @NicholasEllul we decided that the above is not a blocker for this PR. We will follow up in a different PR. You can track the progress here