Add password input (#87)

When using TOTP, a password is required to login. While steamcmd is
perfectly fine with accepting the password as part of the username input
(separated with a space), the way this action is set up, the second
steamcmd invocation where the upload happens would then also use the
password, causing steamcmd to error because the password was provided
without the TOTP code.

Rather than use the TOTP code there again (as proposed in #86), add the
password in the test step (which will cache the credentials), and retain
it from the upload step.

In the configVdf case, the password will be empty, and steamcmd will
ignore it, keeping the previous mechanics.

Author: Rycieos

README.md

@@ -81,6 +81,10 @@ jobs:
 
 The username of the Steam Build Account that you created in setup step 1.
 
+#### password
+
+The password of the Steam Build Account. Both this and `totp` are required together, see below.
+
 #### totp
 
 Deploying to Steam using TOTP. If this is not passed, `configVdf` is required.

action.yml

@@ -6,6 +6,9 @@ inputs:
     required: true
     default: ''
     description: 'The username of your builder account.'
+  password:
+    required: false
+    description: 'The password of your builder account. Required if `totp` is set.'
   totp:
     required: false
     description: 'The TOTP to use for login. If set, `configVdf` will be ignored.'
@@ -94,6 +97,7 @@ runs:
   image: Dockerfile
   env:
     steam_username: ${{ inputs.username }}
+    steam_password: ${{ inputs.password }}
     steam_totp: ${{ inputs.totp }}
     configVdf: ${{ inputs.configVdf }}
     appId: ${{ inputs.appId }}

steam_deploy.sh

@@ -138,7 +138,7 @@ echo "#        Test login             #"
 echo "#################################"
 echo ""
 
-steamcmd +set_steam_guard_code "$steam_totp" +login "$steam_username" +quit;
+steamcmd +set_steam_guard_code "$steam_totp" +login "$steam_username" "$steam_password" +quit;
 
 ret=$?
 if [ $ret -eq 0 ]; then