Review current prompt verbiage and determine casing rules

[andrew-c-tran]

What happened (or feature request):

The current verbiage of errors, dialogs, and prompts in DDEV-UI have been made up on the fly and may not be the most user friendly. Also, minor things such as rules regarding capitalization (i.e. "A Prompt Was Shown." vs "A prompt was shown" need to be decided and applied throughout the application.

[andrew-c-tran]

in thinking of this, while making this decision would it be wise to invest in creating proper i18n support? all application text that doesn't come from the UI can be extracted to a language file and imported in. Though that would create a weird situation with the ability to change languages in the UI but the text coming from the UI remain in english. Perhaps i18n needs to be in lockstep for both cli and ui.

[rfay]

I always feel ugly that we're not doing any kind of translation support in ddev. However, it doesn't seem like a very near goal. But I would support removing strings into a language file. I'm not even sure how one does any support like this in golang.