refactor: Split IPipelineHookContext for Interface Segregation Principle compliance

[thomhurst]

Summary

• Splits IPipelineHookContext (27+ members) into 6 focused sub-interfaces to comply with the Interface Segregation Principle (ISP)
• IPipelineHookContext now inherits from all sub-interfaces, maintaining full backwards compatibility
• Consumers can now depend on only the subset of functionality they need

New Interfaces

Interface	Purpose	Members
IPipelineServices	DI and configuration	ServiceProvider, Get<T>(), Configuration, PipelineOptions
IPipelineLogging	Logging functionality	Logger
IPipelineTools	Command execution and tools	Command, Powershell, Bash, Http, Downloader, Installer
IPipelineEncoding	Serialization and encoding	Json, Xml, Yaml, Hex, Base64, Hasher
IPipelineFileSystem	File operations	FileSystem, Zip, Checksum
IPipelineEnvironment	Environment and build detection	Environment, BuildSystemDetector

Test plan

• Build the core ModularPipelines project: dotnet build src/ModularPipelines/ModularPipelines.csproj -c Release
• Verify existing unit tests pass (CI will run)
• Confirm backwards compatibility - existing code using IPipelineHookContext continues to work

Fixes #1454

🤖 Generated with Claude Code

[github-actions]

Summary

This PR refactors IPipelineHookContext to comply with the Interface Segregation Principle by splitting it into 6 focused sub-interfaces while maintaining full backwards compatibility.

Critical Issues

None found ✅

Suggestions

Typos in XML Documentation (3 occurrences):

1. src/ModularPipelines/Context/IPipelineEncoding.cs:20 - "convering" should be "converting"

   /// Gets helpers for convering XML.

2. src/ModularPipelines/Context/IPipelineEncoding.cs:25 - "convering" should be "converting"

   /// Gets helpers for convering YAML.

These are copy-paste errors from the original interface comments (which also had the same typo). Consider fixing all three occurrences across the new interfaces.

Previous Review Status

No previous comments found.

Verdict

✅ APPROVE - No critical issues

The refactoring is clean and maintains backwards compatibility correctly. The PipelineContext implementation already satisfies all the new interfaces through the existing property implementations, so this is a pure interface reorganization with no breaking changes.