Community addons

Some changes to runbot in order to better test with community addons

When testing a repo which does not contain odoo, but addons from OCA:
* Only test modules from the repo, don't test all of odoo's addons
** opener-hr will only test hr-related addons
* Test Community addons in openerp/addons-to-test instead of openerp/addons to better separate them from official addons
* Add dependency repos field to specify additional addons to fetch
** Some OCA repos depend on modules found in other OCA repos
** These are installed in openerp/openerp/addons-extra-dependencies to better separate them and to avoid testing them which could result in an un-ending chain of repo dependency
* Add function which will find the most likely main branch a PR comes from
** using the git merge-base and git log commands
We could change the system to always only build the main addons from the repository that is being built, always ignoring those from dependency_ids (unless of course the list is explicitly set in repo_id.modules).
Instead of using subdirectories `/addons-to-test`, `/addons-extra-dependencies`, etc., what about just globbing the main repo **before** merging all the dependencies? That should remove a large part of your diff, shouldn't it?