bump axe-core and @axe-core/react

[rhasselle-oddball]

Summary

• bump axe-core and @axe-core/react due to a regression in axe-core
• This error no longer shows up in new version.

Related issue(s)

• Link to ticket created in va.gov-team repo
  department-of-veterans-affairs/va.gov-team-forms#1872

Testing done

Browser testing

Screenshots

Fixes the following issue while developing on the front end:

What areas of the site does it impact?

Development

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

Requested Feedback

(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?

[michaelclement]

Everything work locally for me. Thanks!

[williamphelps13]

Not able to reproduce that error that I was getting previously with these changes running locally so this seems to fix it! Thanks Robert for jumping on this!

[rhasselle-oddball]

Seems there is a legitimate new axe violation according to the new version of axe-core, where previously a test passed but now is failing. looking into this.

[rhasselle-oddball]

New axe rule:
List element has direct children that are not allowed [role=presentation]

[williamphelps13]

LGTM

[Mottie]

LGTM