Update i18n text files

- reorgranize texts to match pattern
usage -> lvl1 specification -> lvl2 usage -> ...
e.g.
errors -> validation -> email
labels -> services -> bcsc
labels -> email
- regression needed afterwards to ensure text is still showing up as the location text is being pulled from is changing.

No file or test paths are named. Start by locating the i18n text files and the existing regression checks that verify displayed text, then trace where each text is loaded. Done means the hierarchy follows the stated usage-to-specification pattern and regression checks confirm the text still appears in the expected locations.

Written by the indexing model from the issue text.