[3.0] Refined allure-js-commons

[epszaw]

Context

This is major allure-js-commons refactoring. The main issue with the current implementation is that each integration provides its own Runtime API. So, it's impossible to create 2nd level integrations (e.g. allure-selenium or allure-axios). Besides, there is some inconsistency with the API's.

The other issue is that commons used to be node-only. In the latest release, we added browser implementation. This PR will adopt it even further, completely replacing the old commons.

The goal of the change is to expose Runtime API from allure-js-commons:

import { label } from "allure-js-commons"

it("test", async() => {
   await label("name", "value");
});

The code above will work in all the supported frameworks.

New Commons architecture:

1. New TestRuntime interface. Provides abstraction for allure-js-commons. All the Runtime API will use TestRuntime, exposed in globalThis.allureTestRuntime variable. Each integration needs to implement its own TestRuntime and ensure it is configured and set to globalise in every scope where Runtime API is supported (e.g. in worker threads in case of parallel execution).
2. Allure Facade — Runtime API methods (exposed as two namespaces, allure-js-commons for async and allure-js-commons/sync for sync alternatives).
3. SDK - set of interfaces and utils used to develop new integrations, such as ReporterRuntime (unified way to store Allure State), Writers, Crypro (node & browser), TestPlan, etc.

Linked issues

fixes #801

All the issues that should be addressed in this PR: https://github.com/allure-framework/allure-js/milestone/1

Checklist

• Sign Allure CLA
• Provide unit tests