Fix nb_NO translation integration

[comradekingu]

Don't think this does anything, but I also can't figure out why the build breaks…

There is an extra / in https://github.com/falzonv/discreet-launcher/pull/77/files#diff-d0c61e533993db7b1d779138cff623d901b1893361374df34f72cc7d92c7a246R33
but that looks to have been removed when merging.

[falzonv]

Yes, I had fixed the extra / in a later commit.

By the way, I see that we forgot to apply the commit for your mail address in #77 (link to the comment: https://github.com/falzonv/discreet-launcher/pull/77/files#r687027736).
I added it to this PR as a suggestion and let you see if you want to include it or not ;-)

Also added the two strings which were missing (thank you!), since this PR is there.

[falzonv]

In "strings.xml", there are three translatable="false" strings that I am not sure what to do with:

• Since they are URLs and my name, they are indeed not translatable and it makes sense to add this label.
• On the other hand, because of this label, Android Studio gives me a warning if they appear in other translations files than the default translation (which is why I removed them for "nb-rNO" and "ru" in 94e6bfa).
  It doesn't break the build but I don't like to let warnings remain for things that could be easily fixed.

Which approach do you think is better?
1/ Remove this "not translatable" label and have the three strings in all translations files.
2/ Keep the label like now and have them only in the main translation file (in that case we need to remove them from this PR).

[comradekingu]

@falzonv Removed since they aren't found in the other translated resources.

[falzonv]

Perfect, let's merge then!