VACMS-18701: updated composer dependencies

[edmund-dunn]

Description

Close #18701

Testing done

Tested locally

Screenshots

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?

Normally, for these updates, we depend on automated testing, so if all automated testing passes, they should be good.

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

Is this PR blocked by another PR?

• DO NOT MERGE

Does this PR need review from a Product Owner

• Needs PO review

CMS user-facing announcement

Is an announcement needed to let editors know of this change?

• Yes, and it's written in issue ____ and queued for publication.
  • Merge and ping the UX writer so they are ready to publish after deployment
• Yes, but it hasn't yet been written
  • Don't merge yet -- ping the UX writer to write and queue content
• No announcement is needed for this code change.
  • Merge & carry on unburdened by announcements

[timcosgrove]

Just curious, how did our tests ever pass given this error? 🙂

[edmund-dunn]

Your guess is as good as mine. I talked this through with Jon. We are looking at a way to test these routes outside of cypress, to help get cypress more performant.

[timcosgrove]

The role is called admnistrator_users here because that's the machine name of the role in the CMS: https://github.com/department-of-veterans-affairs/va.gov-cms/blob/main/config/sync/user.role.admnistrator_users.yml

I don't object to the @ignore but this test would otherwise fail because it's trying to create a user with a non-existent role. We should revert back to the incorrect spelling.

[timcosgrove]

The role is called admnistrator_users here because that's the machine name of the role in the CMS: https://github.com/department-of-veterans-affairs/va.gov-cms/blob/main/config/sync/user.role.admnistrator_users.yml

I don't object to the @ignore but this test would otherwise fail because it's trying to create a user with a non-existent role. We should revert back to the incorrect spelling.