feat: new toggle to hide/show aliased project vulnerability findings

[setchy]

Description

Add a new toggle to the Project Audit Vulnerabilities tab which will show/hide aliased component vulnerabilities within the list.

By default the behavior will remain the same, but the end-user has the option to toggle off the aliased results and see a non-repeating list of component vulns

Addressed Issue

This enhancement aims to avoid end-user confusion around the list of audit vulnerabilities + severities not matching the project vulnerability summary metrics which can occur when mirroring multiple vulnerability sources such as NVD and GHSA.

Additional Details

To avoid any backend API changes, the filtering is performed client-side

Checklist

• I have read and understand the contributing guidelines
• This PR introduces new or alters existing behavior, and I have updated the documentation accordingly

[owasp-dt-bot]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[Copilot]

Pull Request Overview

This PR introduces a UI toggle for audit vulnerabilities that allows users to show or hide aliased component findings, helping to clarify vulnerability metrics.

• Adds a new c-switch toggle in the Project Findings view.
• Implements client-side filtering of findings using a new filtering algorithm.
• Updates localized messages across several language files to support the new toggle.

Reviewed Changes

Copilot reviewed 14 out of 14 changed files in this pull request and generated no comments.

File	Description
src/views/portfolio/projects/ProjectFindings.vue	Introduces a new toggle (c-switch) for aliased findings, implements filtering logic, and persists user preference in localStorage.
src/i18n/locales/*	Adds translations for the new toggle label in multiple languages.

Comments suppressed due to low confidence (1)

src/views/portfolio/projects/ProjectFindings.vue:621

• The method name 'showAliasedFindings' conflicts with the data property of the same name. Consider renaming the method (for example, 'toggleShowAliasedFindings') to avoid ambiguity.

    showAliasedFindings() {