Backport of Added missing output for the terraform apply cli actions into v1.14

[github-actions]

Backport

This PR is auto-generated from #37692 to be assessed for backporting due to the inclusion of the label 1.14-backport.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@mildwonkey
This person should resolve the merge-conflict(s) by either:

• Manually completing the cherry picks into this branch
• Creating a new branch and manually cherry-picking all commits being backported

merge conflict error: unable to process merge commit: "a62eddc33cda0854cb838957ee3e96a8aa1b84b9", automatic backport requires rebase workflow

The below text is copied from the body of the original PR.

---

This fixes the apply cli output to show the actions invoked in bold.

➜ /workspaces/terraform/test-actions (bugfix/terraform-apply-cli-actions-output-missing) $ ../terraform init
Initializing the backend...
Initializing provider plugins...
- terraform.io/builtin/terraform is built in to Terraform
- Reusing previous version of austinvalle/bufo from the dependency lock file
- Using previously-installed austinvalle/bufo v2.0.0

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
➜ /workspaces/terraform/test-actions (bugfix/terraform-apply-cli-actions-output-missing) $ ../terraform plan

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  terraform_data.test will be created
  + resource "terraform_data" "test" {
      + id = (known after apply)
    }

    Actions to be invoked after this change in order:
    action "bufo_print" "success" {
        config {
            color = true
        }
    }


Plan: 1 to add, 0 to change, 0 to destroy. Actions: 1 to invoke.

──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform
apply" now.
➜ /workspaces/terraform/test-actions (bugfix/terraform-apply-cli-actions-output-missing) $ ../terraform apply

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  terraform_data.test will be created
  + resource "terraform_data" "test" {
      + id = (known after apply)
    }

    Actions to be invoked after this change in order:
    action "bufo_print" "success" {
        config {
            color = true
        }
    }


Plan: 1 to add, 0 to change, 0 to destroy. Actions: 1 to invoke.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

terraform_data.test: Creating...
terraform_data.test: Creation complete after 0s [id=8c17cc4c-6b36-3955-2317-0e915d0de500]
Action started: action.bufo_print.success (triggered by terraform_data.test)
Action action.bufo_print.success (triggered by terraform_data.test): 

Bufo: "bufo-cant-find-an-issue.png"

Action complete: action.bufo_print.success (triggered by terraform_data.test)

Apply complete! Resources: 1 added, 0 changed, 0 destroyed. Actions: 1 invoked.

Fixes #37689

Target Release

1.15.x

Rollback Plan

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

CHANGELOG entry

• This change is user-facing and I added a changelog entry.
• This change is not user-facing.

---

Overview of commits

• f13a3ae

• a62eddc

• c12fbe8

• cc4bdf6

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.