[Sub-Issue #549.8] Move M13 (Profiling) to S9 Scalable Applications

[SkafteNicki]

Parent Issue

Part of #549 - New learning session on data engineering

Phase

Phase 2 - Restructure Existing Sessions

Description

Move the Profiling module (M13) from S4 to S9 Scalable Applications, positioning it as the introduction to S9. The rationale is that profiling becomes a natural introduction - to optimize a pipeline, we first need to find the bottlenecks.

Tasks

• Move s4_debugging_and_logging/profiling.md → s9_scalable_applications/profiling.md
• Position as the first module in S9 (before data_loading.md)
• Move any associated exercise_files/ directory
• Update S9 README.md to include the profiling module as the introduction
• Update all internal cross-references to the profiling module
• Search for references in other modules that link to profiling
• Update any relative paths in the moved module
• Verify all links and references still work
• Ensure the module introduces S9 concepts (finding bottlenecks before optimization)

Files to Update

• s4_debugging_and_logging/profiling.md (move to s9_scalable_applications/)
• s9_scalable_applications/README.md
• Any modules that reference the profiling module
• Any exercise files

Dependencies

• Should be done after Phase 1 is complete (S11 modules created)

Acceptance Criteria

• Profiling module successfully moved to S9
• Module is positioned as first module in S9
• All links and references updated and working
• S9 README properly lists profiling as the introductory module
• Content flows naturally into the rest of S9 (data loading, distributed training, inference)
• No broken links remain in the codebase
• Module content emphasizes finding bottlenecks as prerequisite to optimization