Initial follow-ups to the new metrics system

[Cervator]

Some tweaks, ideas, and reminders for later. Follows #2968

• Add a descriptive label to the Metrics Menu describing what it means?
• Add default for the "Owner" field on the metrics and error server configs - "Terasology Community" ?
• Remove the "You can press ENTER..." label on those two screens if we start them out with default values
• Enable the popup when it is time (TODO in StateMainMenu.java)
• (Note from rzats:) Should preShutdown have a hook for disabling telemetry? Since the game is already shutting down
• Consider moving the metrics target port from 80 to something else (leave 80 available for something else)
• Is the Builder2 class needed?
• Eventually consider if we need to tidy up the main menu some, it is getting kinda cluttered
• Eventually switch the dependency exclusion to be done in Terasology rather than the CR as that seems more proper - but that may be a while as it seems like IntelliJ doesn't respect the transitive dependency edits :(
• Update menu.lang with new keys added in menu_en.lang (should contain placeholders)

Edit: wanted to link to this comment: #3024 (comment) as it talks about an example we could also add improvements for :-)

[GabrielXia]

Thanks @Cervator for the suggestions.
Update in pr #3016 commit fda4c8d and 538c4a4

• Add a descriptive label in the Metrics Menu
• Add default "Owner" field "Terasology Community" on the metrics addServerPopup
• Remove the "You can press ENTER..." on the metrics addServerPopup
• Remove disabling telemetry when preShutdown
• Move the collector port from 80 to 14654

Not sure about whether Builder2 class needed yet :(

[Cervator]

Thanks for the updates :-)

Re-opening this as there still are a few todo items left even if they're mostly for later. Did add a new one about translation keys.

[Cervator]

Here's another little stash of notes pulled from #2765 so I can close that one as part of Alpha 8 :-)

• The Crash IssueReporter now opens in the background, which can be confusing (should go to the front, just not be modal)
• Relation to Improve visibility of missing resource / asset scenarios #1402 - steal @iojw's improvement from Added check for insufficient space TerasologyLauncher#392 to also apply in the engine (warning icon showing problems may be active). But could that actually be a new way of opening the CrashReporter in a non-modal mode, which could also be retrofitted to the launcher and elsewhere?
• Implement an outright back-end supported issue reporting system beyond just dumping logs on pastebin or a Google Drive. This would probably involve some existing framework - need to research what's available that could work for us (think a user support style system like ZenDesk, but naturally it has to be at least free and ideally open source. Bonus for integrating with GitHub)
• Implement some metrics gathering users could opt-in for to better understand how the game (or other projects) is being used. Could include how frequently certain warnings or error conditions happen. Could include a more full picture of the user's hardware and such (GPU driver versions?)