fix(core, awesome): remove duplicated step details

[delatrie]

The PR removed a step's details from all parent steps. That only applies to details with identical messages. If the messages differ, all the details are retained.

The implementation is based on the hasSimilarErrorInSubSteps flag introduced in #149, but it makes the flag recursive, which fixes #201.

E2E page objects refactoring

The idea behind the refactoring is to allow defining fixtures to check parts of pages, specifically, the steps of a test on the test result page. Here is the list of changes:

• Split screenshot into screenshot and attachScreenshot. The former can be overridden to attach screenshots of specific elements.

• Make TreePage and TestResultPage derive from CommonPage instead of PageObject.

• Implement StepResultFixture to check steps. Currently, it only contains locators and methods to check status details. Other locators and methods can be added to verify parameters, attachments, etc. Use TestResult.getStepByName or StepResultFixture.getSubstepByName to create a fixture for a step.

  Use StepResultFixture.attachScreenshot to attach a screenshot of the step to Allure (the step must be visible in the report).

• Implement a custom toHaveDetails Playwright matcher. Example:

  import { expect, test } from "../../playwright.js";
  
  /* ... */
  
  test("My step must have message and trace", async () => {
    const step = testResultPage.getStepByName("My step");
    await step.toggleDetails();
    await expect(step).toHaveDetails("Lorem ipsum", "dolor sit amet");
  });

  If an expected value is provided for the step's trace, make sure the step's details are expanded.

  We may add other matches in the future. If the module becomes too large, we may split it into separate modules and combine them into a single extension point as described here.

Other changes

• Define an issue template for @allurereport/e2e.
• Remove an unused variable from environments.test.ts
• Implement an e2e test for nested steps with details

Fixes #201