fix: remove IServiceCollection DI extensions (unnecessary with static API)

Author: CalvinAllen

CLAUDE.md

@@ -69,7 +69,6 @@ The library follows a static facade pattern for ease of use:
 - **Metrics/MetricsProvider.cs** - Manages `Meter` for counters, histograms, gauges
 - **Logging/LoggerProvider.cs** - Wraps `ILoggerFactory` for OpenTelemetry-integrated logging
 - **Exceptions/ExceptionTracker.cs** - Captures exceptions manually and via global handlers
-- **Extensions/ServiceCollectionExtensions.cs** - DI integration via `AddOtel4Vsix()`
 
 ## Key Implementation Details
 

README.md

@@ -258,27 +258,6 @@ VsixTelemetry.Initialize(new TelemetryConfiguration
 
 ---
 
-## Dependency Injection
-
-If your extension uses dependency injection:
-
-```csharp
-using Otel4Vsix.Extensions;
-
-public void ConfigureServices(IServiceCollection services)
-{
-    services.AddOtel4Vsix(config =>
-    {
-        config.ServiceName = "MyExtension";
-        config.OtlpEndpoint = "http://localhost:4317";
-    });
-
-    // Now ILogger<T> is available via DI
-}
-```
-
----
-
 ## Supported Backends
 
 Otel4Vsix exports telemetry via OTLP, which is supported by: