JS Mojo Bindings are currently hosted beneath their WebUI host (e.g chrome://site-engagement/c/b/e/site_engagement_details.mojom.js). This means that the are subject to the GZip rules of their WebUIController, which means that we will have to duplicate resources to provide a GZipped and non-GZipped version of bindings as WebUIs require.

This bug tracks work on moving all bindings to chrome://resources, so that we can have consistently GZipped bindings for all WebUIs to use, and remove the requirement for all WebUIControllers to add their JS Mojo Bindings to their own data source.