use branch name while checking for updates

[ernado]

Should fix #1913

With branch -beta beta:

$ ./stserver update
[  OK  ] Update stserver: Checking for update: SteamCMD: No update available

No update available:
	Current version: 3129892
	Available version: 3129892
	https://steamdb.info/app/600760/

Changed to -beta public

$ ./stserver update
[  OK  ] Update stserver: Checking for update: SteamCMD: Update available

Update available:
	Current build: 3129892
	Available build: 3126493
	https://steamdb.info/app/600760/

Applying update...
[  OK  ] Stopping stserver: Graceful: CTRL+c: 3: OK
[  OK  ] Update stserver: SteamCMD
Redirecting stderr to '/home/stserver/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.

Connecting anonymously to Steam Public...Logged in OK
Waiting for user info...
OK
 Update state (0x5) validating, progress: 0.00 (0 / 0)
 # ...
 Update state (0x61) downloading, progress: 99.64 (286495326 / 287543902)
Success! App '600760' fully installed.
[  OK  ] Starting stserver: LinuxGSM
[  OK  ] Alert stserver: Sending Discord alert

Back to -beta beta

$ ./stserver update
[  OK  ] Update stserver: Checking for update: SteamCMD: Update available

Update available:
	Current build: 3126493
	Available build: 3129892
	https://steamdb.info/app/600760/

Applying update...
[  OK  ] Stopping stserver: Graceful: CTRL+c: 2
# ...

[ernado]

Also I think we should strip the -beta prefix from config and assume it by default and use public branch explicitly if not set, because steamcmd will not use public automatically after being on beta branch, only after specifying -beta public.

But it is out of scope of current fix.

[dgibbs64]

the double +app_info_print "${appid}" has been removed in this pr. I think it was originally used as the first attempt always failed. Not sure if the bug still exists though. I will merge. If the issue pops up again then I will re add

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.