Integrate Weblate into monerujo + remove fuzzy translations

[lucasmz-dev]

https://hosted.weblate.org/projects/monerujo

Being dealt with in a separate branch that we can test everything as safely as possible.
After this is merged, it will be changed to use an automatic GitHub PR + automatic webhooks so that pull is automatic.

Let's see how Weblate behaves with monerujo strings.

Contains #960
Closes #958

[lucasmz-dev]

@m2049r please do not modify source strings from now on! it's fine if you do but don't change translations! It's better to remove them, maintenance wise. It's IMO easier for us to translate things again than to have to go through every string just to see that something might be wrong, and it becomes confusing because sometimes things can be well... adaptations. If you can get those basic changes that disable linting for MissingTranslation, that would be nice.

I still need to figure out how to build to see how things are looking, but it seems OK ATM. These CDATA strings are kind of bad, they show up in a very raw format in Weblate and so the translator still needs to deal with things like \s, weird things like that...

[lucasmz-dev]

Um... weblate deleted the monerujo project 😀
i am very confused
sending them an email

[lucasmz-dev]

@m2049r they restored it ^^
might've been my fault I might have accidentally clicked to ask for approval before the time 😬
you might need to accept an invitation

[lucasmz-dev]

I went over all strings I didn't do, and flagged anything that seemed weird with a comment, will be looking into it in Git history soon to see if it was just an adaptation or if it was a changed string or something
e.g. Node -> Network

[lucasmz-dev]

Hey, @m2049r
Could you build a debug build for this branch? It'd help a lot!

[lucasmz-dev]

I think this might be ready to merge! Need to check if everything seems alright, but after that, and being merged, we can point things properly to this repository and after that ask for libre hosting.

EDIT: actually I need to merge the other translations... let's see

[m2049r]

i still don't think we should be losing good translations

[lucasmz-dev]

I mean I can just go over and just cherry-pick the barebones, but the reason why I went over with this is that we can't for sure know for every language that they are in fact "good translations"
Changing wording can mean very different things in different languages and affect what gender's used, word position, stuff like that, that's the reason I went over like this, the people who want to make these translations work out will and with Weblate any changes in the future can be easily fixed by translators and not go unnoticed

If you're fine with that, I'll do it

[lucasmz-dev]

Weblate has a pretty nice graceful way to deal with "fuzzy" translations, they're marked as needing for editing and show the differences done in the source string, but it doesn't do anything about old commits before integration with it, that's basically what I tried to achieve here, in the end it'd be less work in the end to you and the translators IMO
A lot of translators aren't gonna have the energy/time/want to go through everything, and just wanna be able to translate right off the bat, I am like that for certain apps, especially when they have a messy situation anyway

RN my suggestion is: check #975 and I'll rebase this and then you can see if you want this, so that we can get weblate hosting at least since we'll need those to get things working at a basic level

[m2049r]

if you want, i can look through all translations and remove the non-translated stuff. so this PR would be the barebones of weblate enablement?
not sure what's best