babel extractors are now registered via python entry points,
so there is no need to declare babel extractors in babel configs.
This change is important to make translation work in Django 2.2.
django-babel does not work with Django 2.2 and looks unmaintained
for over two years. The horizon team is thinking to switch the extractor
to enmerkar (a fork of django-babel) to make extraction of translation
string work again near future. It is important to drop the extractor
definition to make the transition smooth.
LBaaS v2 is now the only LBaaS implementation.
It is time to allow translator to translate LBaaS v2 dashboard.
This commit sets up related files according to the infra guide .
Also removes Babel related entries in setup.cfg. They are not
sufficient as Django requires two PO files (django and djangojs).
After this change is merged, I will propose the infra change.
This change can be part of newton release. If it is part of Newton
release of neutron-lbaas-dashboard, translators can translate it
even after the initial Newton release and we can import them
in the stable update release.