Weaving all widgets before application start

The order we currently impose on page load (the application widget) is like:
 1. start all registered services;
 1. weaving all page widgets.

Generally application start logic involves starting multiple services that might need to talk to the server, while page widgets are likely to include error handling, spinning and logging component that requires presence at the very beginning, other UI widgets are  likely to be relatively lazy components that waiting for hub events, it would make sense to **reverse** the current bootstrap order, having widgets instantiated as the first stage before services.