New Route class for much more flexible routing.
Allow language files to be found within modules.
Initial new modular code setup. This includes:

- a brand new Route class that can be used for more flexible route building.
- Complete replacement of Loader and Router class files to make it possible to completely separate Bonfire files from application code. Also will allow possible routing enhancements, like filters, in the future.
- Modifying Common.php to look for core files in the bonfire/core folder also.

From this point forward, these files are ours and we have to own them since Ellislab (or whoever the future owners will be) won't be doing anything for us here.
Get rid  of older modules locations array.
We need an autoloader, so include the new Modules library. This will ultimately provide all of the functions available in our application_helper, as well as a compatibility function for Modules::run() from HMVC that will simply use the new $this->load->controller() to take care of it so that we can deprecate it.
Figuring out some breaks in the load view code when loading modules.
Fixing our admin loading issue where current user was not available.
More fixes to get views working correctly.
Add our Modules::run() method to handle the old HMVC style run call.
Set the new dev version in case anyone installs it.
Bringing the users/view/users view out to the views/ folder where it belongs.
Remove duplicate Route class from the old concept.
Whitespace
No real need to trigger after block rendering. Seems like wasted cycles now.
Let's actually use the new Route library and be an example.
Changing the 'home' feature to make the user be more explicit in where they want the home controller.
Get our edit and create user forms showing up correctly. There's still an issue where the settings module is overriding portions of other settings context controllers.
Reworking the loading of views so it works with our settings contexts again.
Speed up our library loader.

I noticed that the previous versions of the library were calling the find_module() method a redundant number of times, so we're using the new Modules::find() method to get the exact path and unshift that to the top of the places to look for the library.

We could boost performance even a touch more if we simply loaded the file ourself here, like WireDesignz did, but we'll leave it like this for the time being.
did our simple tiny performance boost to the load->models method.