Distributing buildbot confs out of VCS makes no sense
Downgraded prod status of a.r.odoo

a.r.odoo 1.9.0 won't be released as "beta", but still this is newer and
less tested than a.r.openerp 1.9.0
[buildbot] reorg, cfgs for a.r.openerp in related branch

Cherry picked changes done for now in master. The plan is to have for now
a single MANIFEST for all variants, staying in master branch.
But the cfg files for each variant should lie in the corresponding branch only,
to avoid the confusion of having concurrent versions, only one being active.
[buildbot] 80 cfg was pointing to odoo master
[buildbot] separation of builds in a.r.{openerp,odoo}

From now on, the MANIFEST lies in the master branch, but the cfg files differ
in the two branches. Each branch should have build configurations for the
recipe the branch is about.

Builds for a.r.odoo get prefixed with 'odoo-recipe-'
Builds for a.r.openerp still get prefixed with 'recipe-'

(Merge branch 'a.r.openerp-1.9')