Allow custom (re)initialization for Allure lifecycle

### 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](https://github.com/orgs/allure-framework/discussions/2154#discussioncomment-7310619) 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](https://github.com/orgs/allure-framework/discussions/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.

Start by locating AllureLifecycle and its process-wide static singleton initialization. Review how configuration, results-directory selection, and writers are currently constructed, then examine the in-process parallel-run discussion linked in the issue. Done should include a defined way to create or reconfigure isolated lifecycles without relying on the existing singleton.

Written by the indexing model from the issue text.