[tests-only] add e2e test for progress bars

[nabim777]

Description

In this PR, an e2e test is added for the web-app-progress-bar extension.
And currently there is only one web-app-progress-bar named Nyan Cat progress bar, so there is only a test for it.

steps added:

• go to account manage page
• select the option Nyan Cat progress bar

Test run command

pnpm test:e2e --project='progress-bars-chromium'

For more details on how to run the test, please refer to the link here.

Related Issue

• part of [QA] add e2e tests for web-extensions #118

Screenshots (if appropriate):

Following video shows what's automated in the E2E test for web-app-progress-bar extension (added in this PR)

Screencast.from.01-22-2025.04.50.54.PM.webm

How Has This Been Tested?

• test environment:
• CI
• locally
• ...

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

[CLAassistant]

All committers have signed the CLA.

[amrita-shrestha]

i can see multiple extension in one pipeline just want to know how they run, parallel or turn-by-turn ?

Could you describe about hooks and running process in PR description (like hooks run separately for each extension or all extension have same hooks used). So that it will be easy for everyone to review your PR.

Add link to doc to web-extension .
If there is no doc available to run tests for web-extension, how about adding that?

Please keep in mind, while working on QA task, about your team members involvement? If you are working on new task in which most of the staff has not worked before, adding background in description is useful for everyone.