chore(deps-dev): bump pa11y-ci-reporter-html from 6.0.2 to 7.0.0

[julien-deramond]

Description

This PR supersedes #2724 as pa11y tests are not executed in Dependabot PRs.

There are some things we need to test before merging this PR:

• Automatic tests are green just by bumping the dependency
  • See https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/actions/runs/10830125620/job/30049176670?pr=2735.
  • "Upload accessibility results" have been skipped as there are no errors
• Launching the tests locally still works as expected: the HTML report is created and all green
  • npm run docs ; npm run docs-accessibility and file:///Users/xxx/Orange-Boosted-Bootstrap/.pa11y/index.html is clean
• Create a voluntary a11y error detected by pa11y-ci by modifying build/.pa11yci.json to remove #offcanvas and #offcanvasDark rules (see 5777047)
  • CI pa11y-ci test must fail, and we should access to the HTML report
    • CI results
  • Locally, it must fail and generate and HTML report
    • npm run docs ; npm run docs-accessibility

• Revert the fake tests

[netlify]

✅ Deploy Preview for boosted ready!

Name	Link
🔨 Latest commit	2e90abb
🔍 Latest deploy log	https://app.netlify.com/sites/boosted/deploys/66e3c7dacf76210008e0c305
😎 Deploy Preview	https://deploy-preview-2735--boosted.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[julien-deramond]

The only problem I see is that we can see this message: "No files were found with the provided path: .pa11y/. No artifacts will be uploaded.". And the HTML report is not available via the CI execution.

However, it's already an issue on the main branch: see https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/actions/runs/10830594602/job/30050696323#step:10:13

We could merge this PR and try to tackle the issue in a separate PR (if needed).

[vprothais]

Everything is fine for me. Thanks for the detailed process for testing. I learned about the tool and also checked how github actions works.
You can Revert the fake test. I agree with you, the artifact issue can be handled in another PR.