VACMS-19386 Add Checklist template

[randimays]

Description

Adds Resources & Support Checklist template.

Specifics:

• Please review the comments within the diffs; they provide context for some of the changes
• Consistently applied data-next-template attributes on everything in the templates folder. I saw that this was partly implemented and thought it would be helpful to get it done so we can easily identify components from the browser as we develop
  • This also includes removing the data- attributes that pointed specifically to content-build templates to avoid confusion
• Removes the unused custom <Link> component
• Fixes some Typescript errors from the yarn build
• Adjusts Medallia survey code to match the content-build implementation; we won't be able to test this code until it hits staging (known issue that Medallia doesn't work in lower environments than staging)

Design System specifics

• Updates the design system library dependencies
• Updates some components that had already been added to this repo but were out of date (and needed web components)
  • this reduces our ability to have full unit test coverage as you cannot simulate events on web components (this is a known issue in vets-website)
• DST made adjustments made to the names of breakpoints to reduce reliance on the Formation library. These changes are in content-build and vets-website now but needed to be made in next-build (see VADS vs. USWDS values here)

Ticket

• [NextBuild] Migrate the R&S Checklist content type to NextBuild va.gov-cms#19386

Developer Task

Tasks

Beta Give feedback

1. PR submitted against the main branch of next-build.
2. Link to the issue that this PR addresses (if applicable).
3. Define all changes in your PR and note any changes that could potentially be breaking changes.
4. PR includes steps to test your changes and links to these changes in the Tugboat preview (if applicable).
5. Provided before and after screenshots of your changes (if applicable).
6. Alerted the #accelerated-publishing Slack channel to request a PR review.
7. You understand that once approved, you are responsible for merging your changes into main. (Note that changes to main will move automatically into production.)

Testing Steps

• Validate that the Events / Events Listing templates are not negatively impacted by the upgrade to the latest component-library version
• Validated updated generator template for query test files

QA steps

What needs to be checked to prove this works?
What needs to be checked to prove it didn't break any related things?
What variations of circumstances (users, actions, values) need to be checked?

Screenshots

Mobile

Tablet

Desktop

Reviewer

Reviewing a PR

This section lists items that need to be checked or updated when making changes to this repository.

Standard Checks

Tasks

Beta Give feedback

1. Code Quality: Readabilty, Naming Conventions, Consistency, Reusability
2. Test Coverage: 80% coverage
3. Functionality: Change functions as expected with no additional bugs
4. Performance: Code does not introduce performance issues

Merging an Approved Layout

When merging a layout, you must ensure that the content type has been turned on for next-build inside the CMS. This CMS flag must be turned on for editors to preview their work using the next build preview server.

Resource types (layouts) that have not been approved by design should NOT be pushed to production. Ensure that slug.tsx does not include your resource type if it is not approved.

The status of layouts should be kept up to date inside templates.md. This includes QA progress, development progress, etc. A link should be provided for where testing can occur.

Merging a Non-Approved Layout

Your new resource type should not be included inside slug.tsx. Items added here will go into production once merged into the main branch. It is imperative that we do not push anything live that has not been approved.

Ensure that this layout has been added to the templates.md file with the current status of the work.

[randimays]

Closing this and creating a new PR to target an integration branch instead.