i18n: minor reformatting

An msgmerge update seems to have changed the line wrapping heuristics.

Some messages are no longer needed or moved around after source changes.

i18n: update normalized translations

Refactorings moved things around.

i18n: drop translations of push-to-lock strings, removed in 99edd97366e3

A few of the dropped strings had meanwhile been translated. That gave conflicts
when rebasing the po update from 99edd97366e3 and to branch head. That was
resolved by dropping these conflicts.

i18n: drop automaticly introduced bad translations - completely remove previously fuzzy translations, not just the fuzzy markers

This is redoing cb02ca192180, but more aggressively.

msgmerge is aggressively adding fuzzy translations of strings that vaguely
resemble each other. But these translations are bad. And even more bad almost
irreversible when we dropped the fuzzy markers.

Consider for example the translation in 0.4.1 at
https://kallithea-scm.org/repos/kallithea/files/da65398a62fff50f3d241796cbf17acdea2092ef/kallithea/i18n/be/LC_MESSAGES/kallithea.po

"Unauthorized access to resource" is translated to "Несанкцыянаваны доступ да
рэсурсу", but the same translation is also used fuzzily for very different
strings. That can't be good. While the translation of a slightly similar string
might be a good starting point for translators, we don't want to show such
automated and invalid translations to our users. Then it is better to show the
orginal english text, that at least is a clear TODO item and doesn't say
anything wrong.

We thus remove these automaticly generated translations. Some of them were
perhaps marked fuzzy for other reasons, and we might lose a few good
translations. That is still better than having wrong translations. Translators
can also just mark the translation as non-fuzzy and deal with the conflict of
diverging opinion on whether the translation is good. Their statement trumps
our presumption that the automated fuzzy translation is bad.

i18n: normalize headers too

From:
i18n-update normalize-po-files kallithea/i18n/kallithea.pot kallithea/i18n/*/LC_MESSAGES/kallithea.po

i18n: align headers in kallithea.po files

Align the comment headers in all kallithea.po translation files:
- remove the description of the file: for new translations added via
Weblate, this is not updated and it'd contain 'Translations template for
Kallithea'. The name of the language is already present later in the file
in the metadata block.
- remove 'Automatically generated' lines present in some files
- add an empty line below the header block

i18n: remove source code references from kallithea.po files

Remove all comments with source code references from the kallithea.po files.
Such meta data will inherently be outdated, and create unnecessary churn and
repository growth, making it harder to spot actual and important changes.

None of the removed information is actually 'lost', it can be regenerated
via extract_messages/msgmerge, see instructions in kallithea/i18n/how_to.

This commit is part of a series that normalizes the kallithea.po files by
removing all comments, in particular source code references.

i18n: remove fuzzy markers

Remove fuzzy markers in translation files.

This information can be useful to translators in the future and therefore
will be preserved in a separate kallithea-i18n repository with separate
*-i18n branches.

This commit is part of a series that normalizes the kallithea.po files by
removing all comments, in particular source code references.

i18n: remove unused translation strings

Remove translations of strings that are no longer used in Kallithea.

These translations can be useful to translators in the future and therefore
will be preserved in a separate kallithea-i18n repository with separate
*-i18n branches.

This commit is part of a series that normalizes the kallithea.po files by
removing all comments, in particular source code references.

i18n: move list of translators to contributors file

Some .po files in kallithea/i18n contained lists of translators, present
from before usage of Weblate.

Move this information to contributor_data.py so all translation copyright
holders are given credits as CONTRIBUTORS and on the about page.

This commit is part of a series that normalizes the kallithea.po files by
removing all comments, in particular source code references.

i18n: update name/email of 'marcinkuzminski'

In scripts/contributor_data.py, there are already two 'name fixes' for
'marcink' and 'Marcin Kuzminski' to align all contributions with these names
to a specific name and email address.

Assuming they want to use the single email address as specified earlier, we
map the entry 'marcinkuzminski' in the i18n .po files on the same
name/email.

gists: fix typo in translatable string

'was update' -> 'was updated'

i18n: regenerate translations

(according to instructions from kallithea/i18n/how_to)

i18n: pt_BR: fix empty 'Language' entry

This causes 'python2 setup.py update_catalog' to fail with:

File "/usr/lib64/python2.7/site-packages/babel/core.py", line 1094, in parse_locale
raise ValueError('expected only letters, got %r' % lang)
ValueError: expected only letters, got u''

Update translation files

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: Kallithea/Development
Translate-URL: https://hosted.weblate.org/projects/kallithea/kallithea/

spelling: fix inappropriate use of title case

These are not titles or labels, and should not be title cased.

spelling: use "email" consistently

The common English spelling is "email", not "e-mail" (and was indeed
also the most common, but not only, variant in the Kallithea UI).

http://grammarist.com/style/e-mail-email/

i18n: remove translations that 5e7bdfbef29b made both fuzzy and invalid

Get rid of compile_catalog errors.

spelling: fix various typos

This commit fixes various typos or basic English grammar mistakes found by
reviewing the kallithea.pot file.

Full correction of sentences that are not very well formulated, like missing
articles, is out of scope for this commit. Likewise for inconsistent
capitalization of strings like 'Repository group'/'Repository Group'.

Second step in two-part process to rename directories.
This is the actual directory rename.