Enhance `waldo upload` command

[eBardX]

Update the waldo upload command to support the following scenarios:

• Upload the specified build artifact (i.e., specified with a path ending in .app or .apk). An upload token must be specified explicitly (either via the --upload_token option, or via the WALDO_UPLOAD_TOKEN environment variable).
  • If the upload token is an app token, proceed with the upload as in the past.
  • If the upload token is a user token, an app ID must be specified explicitly (either via the --app_id option, or via the WALDO_APP_ID environment variable.
• Upload the latest build artifact from the specified recipe via the currently active user token, and the app ID associated with the recipe.

[laurentsigal]

Update the waldo upload command to support the following scenarios:

Upload the specified build artifact (i.e., specified with a path ending in .app or .apk):

• continue supporting current behavior: the token is specified explicitly (either via the --upload_token option, or via the WALDO_UPLOAD_TOKEN environment variable). This token MUST BE an app token (upload token and app token are synonyms).
• add new behavior: the token is read from the config file, and an app Id is passed as a parameter via the --app_id. in that case, the upload should use the new endpoint.

Upload a recipe:

• add new behavior: in that case, the token must be a user token, and read directly from the config file on disk.

[eBardX]

Uploading a recipe uses the app ID associated with the recipe, yes?

[laurentsigal]

Uploading a recipe uses the app ID associated with the recipe, yes?

yes sir. and it should find the corresponding built artefact, meaning that it does not trigger a build by default.

[eBardX]

Reminder to also adjust the wording of all help surrounding the waldo auth command: it is for authenticating the user rather than authorizing the user.