refactor: move Services container to src/testing/e2e/

The Services dependency injection container was located in src/bootstrap/
but it's only used in E2E tests (src/testing/e2e/). This refactor moves
it to its actual usage location for better code organization.

Changes:
- Moved src/bootstrap/container.rs -> src/testing/e2e/container.rs
- Updated imports to use relative paths within e2e module
- Removed container module from bootstrap (no longer used there)
- Updated documentation references to new location

Rationale:
- Services is exclusively used for E2E testing scenarios
- In production, services are created on-demand per command
- This makes the codebase structure more accurate and explicit

Author: josecelano

src/bootstrap/mod.rs

@@ -1,21 +1,17 @@
 //! Bootstrap Module
 //!
 //! This module contains application initialization and bootstrap concerns.
-//! It handles application lifecycle, dependency injection, logging setup,
-//! and help display.
+//! It handles application lifecycle, logging setup, and help display.
 //!
 //! ## Modules
 //!
 //! - `app` - Main application bootstrap and entry point logic
-//! - `container` - Service container for dependency injection
 //! - `help` - Help and usage information display
 //! - `logging` - Logging configuration and initialization
 
 pub mod app;
-pub mod container;
 pub mod help;
 pub mod logging;
 
 // Re-export commonly used types for convenience
-pub use container::Services;
 pub use logging::{LogFormat, LogOutput, LoggingBuilder, LoggingConfig};

src/config/mod.rs

@@ -25,7 +25,7 @@ use std::path::PathBuf;
 /// Centralizes all deployment-related configuration including file paths,
 /// service connection details, and runtime behavior settings.
 ///
-/// Created once at deployment start and passed to [`Services::new()`](crate::bootstrap::container::Services::new).
+/// Created once at deployment start and passed to [`Services::new()`](crate::testing::e2e::container::Services::new).
 pub struct Config {
     /// Directory containing template files for rendering configurations.
     ///

src/bootstrap/container.rs src/testing/e2e/container.rssrc/bootstrap/container.rs renamed to src/testing/e2e/container.rs

@@ -1,14 +1,20 @@
-//! Dependency injection container for deployment services
+//! Dependency injection container for testing services
 //!
 //! This module provides the `Services` struct that acts as a dependency injection container,
-//! holding all the service clients and template renderers needed for deployment operations.
-//! It centralizes service construction and makes them easily accessible throughout the application.
+//! holding all the service clients and template renderers needed for E2E testing operations.
+//! It centralizes service construction and makes them easily accessible throughout tests.
 //!
 //! ## Services Included
 //!
 //! - **Command clients**: `OpenTofu`, LXD, Ansible clients for external tool interaction
 //! - **Template services**: Template manager and specialized renderers for different tools
 //! - **Configuration**: Centralized configuration management
+//!
+//! ## Usage in Tests
+//!
+//! This container is primarily used in E2E tests to create all necessary service dependencies
+//! in a consistent way. In production, services are created on-demand depending on which
+//! command the user is executing.
 
 use std::sync::Arc;
 use std::time::Duration;
@@ -36,7 +42,7 @@ use crate::shared::Clock;
 /// TODO: Make this configurable via Config in the future
 const REPOSITORY_LOCK_TIMEOUT_SECS: u64 = 30;
 
-/// Service clients and renderers for performing actions
+/// Service clients and renderers for performing actions in tests
 pub struct Services {
     // Command wrappers
     pub opentofu_client: Arc<OpenTofuClient>,

src/testing/e2e/context.rs

@@ -23,7 +23,7 @@
 use tempfile::TempDir;
 use tracing::{info, warn};
 
-use crate::bootstrap::container::Services;
+use super::container::Services;
 use crate::config::Config;
 use crate::domain::environment::state::AnyEnvironmentState;
 use crate::domain::Environment;

src/testing/e2e/mod.rs

@@ -6,6 +6,7 @@
 //!
 //! ## Module Structure
 //!
+//! - `container` - Service dependency injection container for E2E tests
 //! - `context` - Test context configuration and management
 //! - `containers` - Container management for E2E testing scenarios
 //! - `tasks` - High-level testing tasks and workflows
@@ -16,9 +17,13 @@
 //! provisioning, configuration, validation, and cleanup phases to ensure
 //! the entire deployment system works correctly.
 
+pub mod container;
 pub mod containers;
 pub mod context;
 pub mod tasks;
 
+// Re-export for convenience
+pub use container::Services;
+
 // Re-export provisioned container types for backward compatibility
 pub use containers::{ContainerError, RunningProvisionedContainer, StoppedProvisionedContainer};

src/testing/e2e/tasks/container/run_provision_simulation.rs

@@ -25,8 +25,8 @@ use tracing::info;
 
 use crate::adapters::ssh::SshCredentials;
 use crate::application::steps::RenderAnsibleTemplatesStep;
-use crate::bootstrap::container::Services;
 use crate::infrastructure::external_tools::ansible::AnsibleTemplateRenderer;
+use crate::testing::e2e::container::Services;
 use crate::testing::e2e::containers::actions::{SshKeySetupAction, SshWaitAction};
 use crate::testing::e2e::containers::timeout::ContainerTimeouts;
 use crate::testing::e2e::containers::{RunningProvisionedContainer, StoppedProvisionedContainer};

src/testing/mod.rs

@@ -23,6 +23,7 @@ pub use network::{PortChecker, PortCheckerError, PortUsageChecker, PortUsageErro
 
 // Re-export E2E types for convenience
 pub use e2e::{
+    container::Services,
     containers::{ContainerError, RunningProvisionedContainer, StoppedProvisionedContainer},
     context::{TestContext, TestContextType},
 };