2-27-25 Updating web-components package

[Andrew565]

Are you removing or changing a registry.json entryName in this PR?

• No, I'm not changing any entryNames (skip to Summary and delete the rest of this section)
• Yes, I'm removing or changing an entryName

Summary

• Updating web-components package
• I work for the DST

Testing done

• None

Screenshots

N/A

What areas of the site does it impact?

Updates DST web components across the site.

Acceptance criteria

Quality Assurance & Testing

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Linting warnings have been addressed
• Documentation has been updated (link to documentation *if necessary)
• Screenshot of the developed feature is added
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• Did you login to a local build and verify all authenticated routes work as expected with a test user

[va-vfs-bot]

ESLint is disabled

vets-website uses ESLint to help enforce code quality. In most situations we would like ESLint to remain enabled.

What you can do

See if the code can be refactored to avoid disabling ESLint, or wait for a VSP review.

[va-vfs-bot]

ESLint disabled here

[Andrew565]

This file just checks if the custom-elements are all defined, so no axe check is needed here.

[SnowboardTechie]

LGTM 👍🏻