Draft: SteamCMD BETA

What does this MR do and why?

This merge request is the initial beta deployment of SteamCMD functionality. But there will likely be a lot of tweaking required after this and adequate advice too consumers that this is a beta feature would be required.

• BACKEND| Steam Dedicated Server AppID Retrival & Caching
• BACKEND| Host SteamCMD dependency check (lib32stdc++6/lib32gcc1 check SteamCMD docs, and ensure auto installer is updated.
• BACKEND| Initial SteamCMD package refactor from unmaintained wrapper FOS project
  • Final once over and tidy-up of unused bits and pieces from unmaintained wrapper FOS project
• BACKEND| Integration with Crafty application flow
  • SteamCMD & Server Install functionality (Put server build in a thread)
    • Nice to have (popup mini terminal during update showing steamcmd install output.) this could easily just go in the server terminal
  • Update Executable Functionality
    • Just use install but incl validate arg, get appid from gameserver_files/steamapps/manifest
• FRONTEND| Create builder
• FRONTEND| Brainstorm how we're going to populate the server executable config option
• FRONTEND| Add Beta Badges
• FRONTEND| Add server config option for type CUSTOM servers so users can change ping type between TCP and Raknet
• REMOTE| Self-host steamapps catalogue on gitlab pipelines
• DOCUMENTATION| Write supporting documentation and dedicated server compatibility table

• ROADMAP| Steam Credential Login for private/paid dedicated server subscriptions
• ROADMAP| Workshop install by id, and workshop update

Implements #139

Screenshots or screen recordings

TBD

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• Have you checked this doesn't interfere/conflict/duplicate someone elses work?
• Have you fully tested your changes?
• Have you resolved any lint issues?
• Have you assigned a reviewer?
• Have you applied correct labels?