Allow falsy variables in client side translation
What does this MR do?
0 or `` be passed into variables that get used in client side translations.
This was visible for store bells with "0" unconfirmed pickups that just disappeared because of translation throwing an exception.
How confident are you it won't break things if deployed?
Links to related issues
- added a test, or explain why one is not needed/possible...
- no unrelated changes
- asked someone for a code review
- joined #foodsharing-beta channel at https://slackin.yunity.org
- added an entry to CHANGELOG.md (description, merge request link, username(s))