Restructure to start using DI, misc. other items

In a move that helps with #96 and #115 these are the first steps towards dropping the use of `Joomla\Factory` and implementing DI code.

Essentially, for what is being used in the codebase currently, we don't actually need to register anything to `Joomla\Factory`, so our first version of DI is a hybrid Factory/DI implementation (similar to that David & Don use in Cobalt) and the application and database objects are registered as service providers and globally accessible via `JTracker\Container::retrieve($key);`.  Other objects can be refactored out of the application and into the DI structure if this works for everyone, and as the parent Framework completely shifts Factory out and embraces the DI Container, we can shift away from our hybrid solution to a more pure implementation.

There's also a few miscellaneous admin tasks included here:

- Dependency updates
- Refactoring out `JPATH_BASE` (similar to what I just did with the Framework)
- Drop a couple of unused language files