Closes #42: Smoke/Regression test for delayjs script

[jeawhanlee]

Description

Added Smoke/VR test for delayjs

Fixes #42

Type of change

• New feature (non-breaking change which adds functionality).

Is the solution different from the one proposed during the grooming?

Slightly different, The grooming proposed a solution of automating the the whole theme switching before creating a backstop reference for VR testing but it got complicated to implement so what we currently have is separate script command for various test theme candidate.

Checklists

Generic development checklist

• My code follows the style guidelines of this project, with adapted comments and without new warnings.
• I have added unit and integration tests that prove my fix is effective or that my feature works.
• The CI passes locally with my changes (including unit tests, integration tests, linter).
• Any dependent changes have been merged and published in downstream modules.
• If applicable, I have made corresponding changes to the documentation. Provide a link to the documentation.

Test summary

• I triggered all changed lines of code at least once without new errors/warnings/notices.
• I validated all Acceptance Criteria of the related issues. (If applicable, provide proof).
• I validated all test plan the QA Review asked me to.

If not, detail what you could not test.

Please describe any additional tests you performed.

[Mai-Saad]

@jeawhanlee Thanks for the PR. Please find usability test notes below.
1- Currently, For scenario 1. We need to use cmd to run the test against specific theme i.e npm run test:delayjs:astra=> We need to enhance that (may be other GH) so single cmd i.e npm run test:delayjs will run the same scenario n times , each with specific theme
2- When we have theme x active and we run vs theme y, test will fail then if we rerun will pass => further investigation is needed here => update : now retesting this, sometimes pass, others fail so we shall keep an eye on this for upcoming execution