Closes #176: Backstop tests not working as expected for LLCSSBG & LRC tests when run generally

[jeawhanlee]

Description

Creates backstop references for general test run.

Fixes #176
Fixes issue with backstop test not running as expected during general test run.

Type of change

• Bug fix (non-breaking change which fixes an issue).

Detailed scenario

• Switch to develop and do a general test run (npm run test:e2e)

Technical description

Documentation

Added new step in feature files to create backstop references based on tags

New dependencies

N/A

Risks

N/A

Mandatory Checklist

Code validation

• I validated all the Acceptance Criteria. If possible, provide screenshots or videos.
• I triggered all changed lines of code at least once without new errors/warnings/notices.
• I implemented built-in tests to cover the new/changed code.

Code style

• I wrote a self-explanatory code about what it does.
• I protected entry points against unexpected inputs.
• I did not introduce unnecessary complexity.
• Output messages (errors, notices, logs) are explicit enough for users to understand the issue and are actionnable.

[Mai-Saad]

We need to confirm:

• running llcssbg only is green
• Running LRC only is green
• running all e2e => llcssbg is green , no regression compared to dev for other tests
• no backstop reference is created if we only run smoke tests
• backstop tabs at e2e have results (no 0 passed, 0 failed case)

[Mai-Saad]

For llcssbg ✔️

• tests are green
  

• we have 1 template failing to be investigated in separate GH
  

• backstop not having 0 passed/0failed ✔️

For lrc ✔️

• test is passing
  

• some templates fails at backstop which is known and we shall have GH related Adding toggle for lrc json templates to control flaky templates #154

• no backstop was created when running smoke test (1 test is failing there cause of error in debug.log that shall be covered here Ignore random errors in certain cases wp-rocket-e2e-test-helper#3)

• For all e2e run , we have 3 failed tests, one for timeout to be investigated later and have separate GH if needed. and 2 due to errors in debug that will be ignored