run all commands silently

To avoid leaking any potentially sensitive information, all commands are now run
without logging to the console. Logging can be enabled by turning on debug logging
as described at https://docs.github.com/en/actions/how-tos/monitor-workflows/enable-debug-logging.

Updates tailscale/corp#33405

Signed-off-by: Percy Wegmann <percy@tailscale.com>

update v4 to v4.0.2

stop echoing tailscale status to console

Updates #201

Signed-off-by: Percy Wegmann <percy@tailscale.com>

miscellaneous cleanup items from upgrading to TypeScript action

Updates tailscale/corp#32821

Signed-off-by: Percy Wegmann <percy@tailscale.com>

Merge pull request #195 from tailscale/max/test-target-connectivity-c…

…heck

Added argument to test targets connectivity

Merge pull request #195 from tailscale/max/test-target-connectivity-c…

…heck

Added argument to test targets connectivity

Merge pull request #196 from tailscale/max/sanitize-hostnames

action: auto-sanitize default or error on invalid user-defined hostname

Merge pull request #181 from tailscale/mpminardi/windows-unattended-mode

{.github/workflows,action.yml}: run windows in unattended mode

Merge pull request #178 from tailscale/max/add-retry

action: add retry on tailscale up to make the action more reliable

action.yml: properly remove temporary files after downloading

Remove `.tgz` and `.msi` files after they have been downloaded. This was
the behaviour of the action previous to `v3.2.0`, but our logic for
caching removed the deletion of these files.

Can look at downloading these to temp folders to avoid the more complex
logic here as a follow up, but this should unblock / fix the immediate
regression.

Also, on Windows, write `tailscale.log` to the temp dir.

Also, on MacOS, delete the `tailscale` directory that was used to build the `tailscale(d)` commands.

Updates: #170

Co-authored-by: Mario Minardi <mario@tailscale.com>
Signed-off-by: Percy Wegmann <percy@tailscale.com>