Revert GHA Tugboat integration

[JunTaoLuo]

Description

Resolves #16884. This will revert the changes from #16279 #16562 and #16739. These changes will return to using webhook integration for Tugboat previews.

Testing done

Webhooks tested using the following steps with a test PR.

QA steps

Testing this change requires turning on the Tugboat webhook which will be disruptive since duplicate Tugboat previews will be created. When testing make an announcement in the CMS channel so other developers are aware of the issue and clean up duplicated previews once testing is done. To test this change, make a PR that targets this branch and perform the following actions which tests for routine PR actions including opening, updating, closing, reopening and merging.

As any user who can open PRs on this repo

1. Turn on Tugboat webhooks in the repository settings and enable sending PR notifications
   • Navigate to Settings >> Webhooks >> https://dev.va.gov/cms-tugboat/... >> Edit
   • Under "Which events would you like to trigger this webhook?" choose "Let me select individual events."
   • Check "Pull requests" and do not uncheck "Pushes"
   • Click "Update Webhook"
2. Open a PR targeting this branch 16884-revert. I recommend making a small documentation change that can be reverted in step 6.
   • Ensure required CI workflows are triggered and completes successfully
   • Ensure Tugboat deployments are triggered and the status and links are posted to the PR. E.g.

• Ensure previews are created and can be accessed

3. Update the PR with an new commit
   • Ensure required CI workflows are triggered and completes successfully
   • Ensure previews are rebuilt on PR updates, ensure the SHA of the commit used to build the preview is the updated commit.
   • Ensure previews are created and can be accessed
4. Close the PR without merging
   • Ensure Tugboat deployments status is updated (i.e. deployment is destroyed). E.g:

• Ensure previews are deleted

5. Re-open the PR
   • Ensure required CI workflows are triggered and completes successfully
   • Ensure Tugboat deployments are triggered and the status and links are posted to the PR
   • Ensure previews are created and can be accessed
6. Merge the PR to this branch
   • Ensure Tugboat deployments status is updated (i.e. deployment is destroyed)
   • Ensure previews are deleted
7. Clean up changes made during these tests

• Revert the the changes contained in the PR so it does not affect this PR functionally.
• Turn off the Tugboat PR webhook
• Review Tugboat previews and delete any duplicates created during testing

Definition of Done

• Documentation has been updated, if applicable.
• Tests have been added if necessary.
• Automated tests have passed.
• Code Quality Tests have passed.
• Acceptance Criteria in related issue are met.
• Manual Code Review Approved.
• If there are field changes, front end output has been thoroughly checked.

Select Team for PR review

• CMS Team
• Public websites
• Facilities
• User support
• Accelerated Publishing

[ndouglas]

Given the disruptiveness of testing these changes and the fact that we know we had a working system under the prior model just a few weeks ago, I'm inclined to just do a code-level review on this. Thoughts?

[ndouglas]

Seems legit; I have no notes.

[JunTaoLuo]

Given the disruptiveness of testing these changes and the fact that we know we had a working system under the prior model just a few weeks ago, I'm inclined to just do a code-level review on this. Thoughts?

Yea I think that is fine, especially since I did test the webhooks after hours two days ago.

[github-actions]

GitHub Workflows (.github/workflows/*.yml)

Have you...

• pinned all affected GitHub Actions at a specific commit by SHA?
• reviewed the source code of the action at the commit you are pinning?
• confirmed that no GitHub security measures are being bypassed?
• checked for any injection of user content into protected contexts?
• reviewed Security hardening for GitHub Actions?
• reviewed GitHub Workflows?