User facing messages/warnings/errors should be localized, and documented

[radical]

Prompted by #78755 (comment)

The shipping tasks in src/tasks have user facing strings in the form of:

• messages (Log.LogMessage - especially the Normal, and High importance ones)
• warnings
• errors

These need to be identified, and localized.

Questions:

• Do all 3 need that treatment?
• Are there any existing cases where such messages are localized that can be used as examples to do this?
• Do the user-facing Errors need to be assigned codes too?
• Where, and how should the Errors, and Warnings be documented?

cc @akoeplinger @maraf @lewing @steveisok