openstack/networking-bgpvpn - networking-bgpvpn - OpenDev: Free Software Needs Free Tools

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.
Change-Id: I997dc7d2f572a9be627f7aa5d463f20ee23895ff

Currently strings in Django templates cannot be translated
because the current recommended file pattern "templates/**.html"
does not match Django templates in subdirectories.
This needs to be "**/templates/**.html".
Change-Id: I8d68d847edebce37e37e671a1ad3eadddd4354e8
Closes-Bug: #1747453 

Files required to translation support are added by this commit.
For more detail, see Enabling Translation Infrastructure section in
the Project Creators' Guide [1] (especially, "More complex cases" section)
Also this commit changes the following:
* Add babel files for BGPVPN dashboard.
* Use underscore translation domain name in networking_bgpvpn/_i18n.py
 (underscore version is expected by the infra script.)
* Use an original translation domain name for networking_bgpvpn_heat.
* Add *.pot to .gitignore as we don't have POT files in our git repo.
[1] https://docs.openstack.org/infra/manual/creators.html#enabling-translation-infrastructure
Change-Id: I75060710748323bdfe74be1cbaa8fa5736feafc9