added code to run the suites of the current (window) project, added plugin configuration, small refactor

I added some conveniences for the plugin

1. Now tests_dir is configurable globally and per project. As side effect of this, I renamed the UnitTesting.sublime-settings file that stores the recent packages to UnitTesting.recently-used that has more sense
2. There is now six commands available in the `Command Palette` (and they are prefixed with "UnitTesting")
    * UnitTesting: Run any project test suite
    * UnitTesting: Run any project test suite (Async)
    * UnitTesting: Run any project test suite (Deferred)
    * UnitTesting: Run current project test suite
    * UnitTesting: Run current project test suite (Async)
    * UnitTesting: Run current project test suite (Deferred)

All the **current project** versions take the name of the project from the currently opened project, if a name can't be infered, it just asks for the project name as the other versions of the command call

Why?

`sublime.active_window().project_data()` returns you the project configured build system as well as the project open folders, I don't think we need all this information unless what do you want to do is to not use the `settings` section of the project configuration (that is what view().settings() return back).

You don't really need to open a buffer to have a view in the current window, there is always a view in the window (or it should be) even if it has no any buffer on it