refactor: remove redundant naming in infrastructure files

Fixed naming ambiguity by removing duplicate prefixes:
- builders/dockerfile_builder.py  builders/dockerfile.py
- factories/factories.py  factories/service.py
- health/health_checks.py  health/checks.py
- models/pydantic_models.py  models/validation.py

Rationale:
- Directory name already indicates purpose (builders/, factories/, etc.)
- Redundant suffixes create ambiguity and confusion
- Follows DRY principle and proper naming conventions
- Cleaner imports: 'from builders.dockerfile import DockerfileBuilder'
  vs 'from builders.dockerfile_builder import DockerfileBuilder'

Updated:
- __init__.py with new import paths
- README.md with correct filenames in directory structure

No breaking changes - all imports still work through main __init__.py

Author: DeanLuus22021994

.devcontainer/infrastructure/README.md

@@ -23,28 +23,37 @@ Components are organized by purpose in subdirectories:
 
 ```text
 infrastructure/
-├── core/                      # Foundational classes
+├── core/                # Foundational classes
 │   ├── __init__.py
-│   ├── base.py               # Abstract base classes
-│   └── config.py             # Configuration dataclasses
-├── builders/                  # Builder patterns
+│   ├── base.py         # Abstract base classes (ContainerService, DatabaseService)
+│   └── config.py       # Configuration dataclasses
+├── builders/            # Builder patterns
 │   ├── __init__.py
-│   └── dockerfile_builder.py # Template Method for Dockerfiles
-├── factories/                 # Factory patterns
+│   └── dockerfile.py   # Template Method for Dockerfiles
+├── factories/           # Factory patterns
 │   ├── __init__.py
-│   └── factories.py          # Service and component factories
-├── health/                    # Health check strategies
+│   └── service.py      # Service and component factories
+├── health/              # Health check strategies
 │   ├── __init__.py
-│   └── health_checks.py      # Strategy pattern implementations
-├── models/                    # Data models
+│   └── checks.py       # Strategy pattern implementations
+├── models/              # Data models
 │   ├── __init__.py
-│   └── pydantic_models.py    # Pydantic validation models
-├── testing/                   # Test utilities
+│   └── validation.py   # Pydantic validation models
+├── testing/             # Test utilities
 │   ├── __init__.py
+│   └── fixtures.py     # Pytest fixtures
+├── cli.py               # Command-line interface (entry point)
+├── __init__.py          # Module exports
+└── README.md            # This file
+```
+
+├── testing/                   # Test utilities
+│   ├── **init**.py
 │   └── fixtures.py           # Pytest fixtures
 ├── cli.py                     # Command-line interface
-├── __init__.py               # Module exports
+├── **init**.py               # Module exports
 └── README.md
+
 ```
 
 ## Architecture

.devcontainer/infrastructure/__init__.py

@@ -23,7 +23,7 @@
     DatabaseService,
     MessageBrokerService,
 )
-from .health.health_checks import (
+from .health.checks import (
     HealthCheck,
     HttpHealthCheck,
     TcpHealthCheck,
@@ -37,17 +37,17 @@
     ServiceConfig,
     DockerComposeConfig,
 )
-from .models.pydantic_models import (
+from .models.validation import (
     EnvironmentConfigModel,
     ServiceConfigModel,
     DockerComposeConfigModel,
     PortModel,
 )
-from .factories.factories import (
+from .factories.service import (
     DaprComponentFactory,
     ServiceFactory,
 )
-from .builders.dockerfile_builder import (
+from .builders.dockerfile import (
     DockerfileBuilder,
     DevelopmentDockerfileBuilder,
     ProductionDockerfileBuilder,