Standalone command-line tool follow-up

[0x2b3bfa0]

Continuation of https://github.com/iterative/terraform-provider-iterative/pull/610

Functionality

Note that the Visual Studio Code Remote use case already provides both capabilities out of the box, so we don't have to implement anything on our code base yet if we only prioritize that use case.

• https://github.com/iterative/terraform-provider-iterative/issues/291
• https://github.com/iterative/terraform-provider-iterative/issues/531

User Experience

• [x] https://github.com/iterative/terraform-provider-iterative/issues/638
• [ ] Allow users to specify custom identifiers with a random suffix
• [ ] Provide sensible logger output for TTY and non-TTY formats
• [ ] Separate commands to list logs & general status[^2]

[^1]: Unlike in Terraform HCL, values must not contain arithmetic expressions (e.g. 60*60*24 is not valid, but 86400 is valid). Also, declaring multiple resource blocks produces undefined behavior; i.e. defined behavior, but too contrived to explain in a footnote; definitely not what users expect. [^2]: With a special case for $parallelism > 1$ where users can filter logs for a single task.

[dacbd]

after a "Provide sensible logger output for TTY and non-TTY formats" I think an attach type command would be helpful to "live" monitor a task.

[0x2b3bfa0]

Part of “Separate commands to list logs & general status” to my mind. It could be log --follow or similar?

[0x2b3bfa0]

Closing in favor of https://github.com/iterative/terraform-provider-iterative/issues/666, which holds the remaining items 😈