Add SES lockdown and Sentry to all pages

[Gudahtt]

When the SES lockdown was added in #9729, the lockdown and the Sentry initialization were migrated from the main bundle into separate modules, which were run as separate <script> tags. These extra tags were accidentally omitted for home.html and notification.html. As a result Sentry was not initialized on these pages, so any errors thrown on them would not be collected. They also do not benefit from the SES lockdown.

The SES lockdown and Sentry initialization modules have been added to both pages where they were missing.

[metamaskbot]

Builds ready [7b1ee52]

• builds: chrome, firefox, opera
• bundle viz: background, ui, inpage, contentscript, ui-libs, bg-libs, phishing-detect
• dep viz: background
• all artifacts

Page Load Metrics (586 ± 39 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	48	90	60	11	5
		domContentLoaded	332	722	585	82	39
		load	333	724	586	82	39
		domInteractive	331	721	585	82	39

[Gudahtt]

Steps to reproduce:

1. Introduce an error somewhere in the application UI. Usually I add a new Error("test") to the render function of the Home component.
2. Build the extension using yarn dist (Sentry errors aren't reported in dev builds)
3. Load the page with the error and open the network tab of dev tools
4. Reload the page, and unlock if necessary. You should see the error page.

On develop, there will be no network call to report the error to Sentry. With this PR, there will be a network call.