Explicitly enable application and core modules

The application and core modules must now be explicitly set in the bootstrap.php instead of magically being added in the core behind the scenes. This gives the user total control and flexibility over modules and makes all modules optional.

Kohana::include_paths() method has been removed, the only difference between this and Kohana::modules() is that it included the application and core module paths. Now that these two modules are included in Kohana::$_modules there's no need for the method to exist, likewise with Kohana::$_paths.

In the refactor of Kohana::modules(), array_reverse() is used before setting and getting modules. This makes it so Kohana::$_modules internally stores modules in the correct order, however externally it works in the same "top to bottom" fashion. As array_reverse() is now in one place, other methods such as find_file() don't have to worry about reversing the modules array before use.
Oh right, yeah it does depend on this little change to core https://github.com/kohana/core/pull/515/files but updating to 5.4 has already been discussed and accepted so there's no chance it would get rejected. However I do accept that I should have used array() or waited for 515 to be merged, I'm still getting used to making small, non-dependant PRs.