Allow custom (re)initialization for Allure lifecycle

[delatrie]

Context

Currently, AllureLifecycle is initialized once per process. The static singleton is then used until the process ends.

The following scenarios are not supported due to such limitations:

• Provide a user-defined initialization to specify the following at runtime:
  • a configuration, including the results directory (although, a workaround exists).
  • a writer (e.g., a message-based writer instead of the file system one).
• Executing separate test framework runs in-process (see discussion 2536):
  • There is no way to reconfigure the lifecycle once it's created.
  • There is no way to isolate lifecycles for separate parallel in-process runs.

[flibustier7seas]

We would greatly benefit from having the ability to create multiple AllureLifecycle instances as needed and publish test results programmatically from a specific instance (instead of relying on allurectl).

Currently, we have a custom testing framework that continuously runs performance/availability tests in a production environment, and we would like to leverage Allure for visualizing the test results. However, the current functionality does not provide a convenient way to achieve this.