feat: enhance E2E testing setup and model reporting

- Added a new fixture to manage runtime report artifacts in a writable temp directory during E2E tests, addressing permission issues in local CI/dev environments.
- Updated `conftest.py` to include a requirements.txt file in the model packaging path for training activities.
- Refactored existing fixtures to use `pytest.fixture` instead of `pytest_asyncio.fixture` for better compatibility.
- Enhanced the `Reports` class to include a target alias for report metrics, ensuring compatibility with Evidently's reporting requirements.
- Introduced new test scenarios to validate the handling of missing and whitespace-only `date_column` inputs in the training workflow.

These changes improve the robustness of the E2E testing framework and enhance the clarity of model reporting metrics.

tests/utils/models/test_experiment_status.py

@@ -46,7 +46,7 @@ def test_experiment_status_comparison():
     assert ExperimentStatus.ORCHESTRATOR_VALIDATION_ERROR == 'ORCHESTRATOR_VALIDATION_ERROR'
     assert ExperimentStatus.ORCHESTRATOR_WAITING_PROC == 'ORCHESTRATOR_WAITING_PROC'
     assert ExperimentStatus.TRAINING_SUCCESS == 'TRAINING_SUCCESS'
-    assert ExperimentStatus.TRAINING_ERROR != 'TRAINING_SUCCESS'
+    assert str(ExperimentStatus.TRAINING_ERROR) != 'TRAINING_SUCCESS'
 
 
 def test_experiment_status_access_by_name():