fix: pass Impersonate option to extractor HTTP client (#37)

The `Impersonate` field from extractor config was not being forwarded
to `NewHTTPClientOptions` when building the extractor context in
`FromURL()`. This meant that even when `impersonate: true` was set
in the extractor YAML configuration, the HTTP client would never
call `NewChromeClient()`, effectively making TLS fingerprint
impersonation a no-op for all extractors.

This one-liner adds the missing field passthrough, aligning
`Impersonate` with the other options (`Proxy`, `DisableProxy`, etc.)
that are already forwarded correctly.

Co-authored-by: eagle1maledetto <eagle1maledetto@users.noreply.github.com>

Author: eagle1maledetto

internal/extractors/util.go

@@ -88,6 +88,7 @@ func FromURL(url string) *models.ExtractorContext {
 					DownloadProxy: cfg.DownloadProxy,
 					Proxy:         cfg.Proxy,
 					DisableProxy:  cfg.DisableProxy,
+					Impersonate:   cfg.Impersonate,
 				},
 			),
 		}