ci: remove lighthouse redundancy in pipeline

[Rajdeepc]

Description

This PR removes redundant Lighthouse checks from the CI pipeline to optimize build times and reduce unnecessary executions. Lighthouse audits were being run multiple times, leading to redundant checks without added value. This change ensures that performance and accessibility tests are still covered without the extra overhead.

Motivation and context

Removing redundant Lighthouse runs helps streamline our CI pipeline, improving efficiency and reducing execution time without impacting the quality of our audits.

How has this been tested?

• Verified that the pipeline runs successfully without the redundant Lighthouse steps.
• Ensured that other CI checks, including performance and accessibility tests, continue to function correctly.
• Checked logs to confirm that necessary audits are still performed where required.

Types of changes

• Chore (minor updates related to the tooling or maintenance of the repository, does not impact compiled assets)

Checklist

• I have signed the [Adobe Open Source CLA](http://opensource.adobe.com/cla.html).
• My code follows the code style of this project.
• If my change required a change to the documentation, I have updated the documentation in this pull request.
• I have read the [CONTRIBUTING](https://github.com/adobe/spectrum-web-components/blob/main/CONTRIBUTING.md) document.
• I have reviewed the Accessibility Practices for this feature, see: [Aria Practices](https://www.w3.org/TR/wai-aria-practices/).

Let me know if you need any modifications! 🚀

[changeset-bot]

⚠️ No Changeset found

Latest commit: 716fb1d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Branch preview

• Documentation Site
• Storybook

Review the following VRT differences

When a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:

• Spectrum | Light | Medium | LTR
• Spectrum | Dark | Large | RTL
• Express | Light | Medium | LTR
• Express | Dark | Large | RTL
• Spectrum-two | Light | Medium | LTR
• Spectrum-two | Dark | Large | RTL
• High Contrast Mode | Medium | LTR

If the changes are expected, update the current_golden_images_cache hash in the circleci config to accept the new images. Instructions are included in that file.
If the changes are unexpected, you can investigate the cause of the differences and update the code accordingly.

[github-actions]

Tachometer results

Currently, no packages are changed by this PR...

[coveralls]

Pull Request Test Coverage Report for Build 13787310318

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 97.977%

---

Totals
Change from base Build 13763875714:	0.0%
Covered Lines:	33650
Relevant Lines:	34148

---

💛 - Coveralls

[rubencarvalho]

Nice! Let's revisit performance testing in the future, in a more relevant way.