views: add cloud view

[bschaatsbergen]

Closes #35159

The cloud backend implements a retry mechanism for its client, go-tfe. Currently, retry messages from this logic were not rendered through a view, so the -json flag was not respected. This resulted in mixed (non-pure JSON) output in the terminal whenever retry messages were printed.

This PR introduces a new view: cloud, which handles rendering output in human-readable or machine-readable format (JSON) from cloud-specific operations.

The PR works around the current lack of native support for views in the backends. To work around this limitation, we expose the ViewType and View to the CLI options, which we pass down to the cloud backend.

 $ go test -run "TestNewCloud" -v
=== RUN   TestNewCloudHuman_RetryLog
=== RUN   TestNewCloudHuman_RetryLog/first_retry,_no_output
=== RUN   TestNewCloudHuman_RetryLog/second_retry,_server_error
=== RUN   TestNewCloudHuman_RetryLog/subsequent_retry_with_elapsed_time
=== RUN   TestNewCloudHuman_RetryLog/retry_with_429_status,_no_output
--- PASS: TestNewCloudHuman_RetryLog (0.00s)
    --- PASS: TestNewCloudHuman_RetryLog/first_retry,_no_output (0.00s)
    --- PASS: TestNewCloudHuman_RetryLog/second_retry,_server_error (0.00s)
    --- PASS: TestNewCloudHuman_RetryLog/subsequent_retry_with_elapsed_time (0.00s)
    --- PASS: TestNewCloudHuman_RetryLog/retry_with_429_status,_no_output (0.00s)
=== RUN   TestNewCloud_unsupportedViewDiagnostics
--- PASS: TestNewCloud_unsupportedViewDiagnostics (0.00s)
=== RUN   TestNewCloud_humanViewOutput
=== RUN   TestNewCloud_humanViewOutput/no_param
=== RUN   TestNewCloud_humanViewOutput/single_param
--- PASS: TestNewCloud_humanViewOutput (0.00s)
    --- PASS: TestNewCloud_humanViewOutput/no_param (0.00s)
    --- PASS: TestNewCloud_humanViewOutput/single_param (0.00s)
=== RUN   TestNewCloud_humanViewDiagnostics
--- PASS: TestNewCloud_humanViewDiagnostics (0.00s)
=== RUN   TestNewCloudJSON_RetryLog
=== RUN   TestNewCloudJSON_RetryLog/attempt_0,_no_output
=== RUN   TestNewCloudJSON_RetryLog/attempt_1,_server_error
=== RUN   TestNewCloudJSON_RetryLog/subsequent_retry_with_elapsed_time
=== RUN   TestNewCloudJSON_RetryLog/retry_with_429_status,_no_output
--- PASS: TestNewCloudJSON_RetryLog (0.00s)
    --- PASS: TestNewCloudJSON_RetryLog/attempt_0,_no_output (0.00s)
    --- PASS: TestNewCloudJSON_RetryLog/attempt_1,_server_error (0.00s)
    --- PASS: TestNewCloudJSON_RetryLog/subsequent_retry_with_elapsed_time (0.00s)
    --- PASS: TestNewCloudJSON_RetryLog/retry_with_429_status,_no_output (0.00s)
=== RUN   TestNewCloud_jsonViewOutput
=== RUN   TestNewCloud_jsonViewOutput/no_param
=== RUN   TestNewCloud_jsonViewOutput/single_param
--- PASS: TestNewCloud_jsonViewOutput (0.00s)
    --- PASS: TestNewCloud_jsonViewOutput/no_param (0.00s)
    --- PASS: TestNewCloud_jsonViewOutput/single_param (0.00s)
=== RUN   TestNewCloud_jsonViewDiagnostics
--- PASS: TestNewCloud_jsonViewDiagnostics (0.00s)
PASS
ok      github.com/hashicorp/terraform/internal/command/views   0.902s

[liamcervante]

I think you need to run make copyright-fix to pass the code consistency checks!

[liamcervante]

You could get rid of the TFCRetryHook function entirely now, and just call the RetryLog function directly from wherever this was being called before.

[sebasslash]

These changes look great 😄. I suppose an open question, of which I don't have a strong opinion, is whether we want to suppress these messages unless a log level is set by TF_LOG. I personally prefer verbose output, but it may introduce more noise than some people would prefer.

Some optional 💅 suggestions below

[liamcervante]

Looks good to me! Probably good to wait for Sebastian's approval too

[sebasslash]

🚀 Nice work!

[github-actions]

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.