chore: Create FDv2 polling and fallback data source

[jsonbailey]

Note

Introduces the FDv2 polling data path with fallback signaling and supporting infrastructure.

• New Impl::DataSystem::PollingDataSource (Initializer/Synchronizer) with periodic fetch, recoverable/unrecoverable error handling, x-launchdarkly-env-id capture, and FDv1 fallback via x-launchdarkly-fd-fallback
• HTTP requesters: HTTPPollingRequester (FDv2 /sdk/poll) and HTTPFDv1PollingRequester (FDv1 /sdk/latest-all), with ETag handling, selector/filter query params, JSON parsing, and graceful stop
• Payload parsing helpers: polling_payload_to_changeset (FDv2 events) and fdv1_polling_payload_to_changeset (latest-all) producing ChangeSets
• DataSystem factory methods now expose polling_ds_builder and fdv1_fallback_ds_builder; default/streaming/polling configs wire them in
• Result now carries optional headers; ChangeSetBuilder.no_changes uses Selector.no_selector
• Legacy Impl::DataSource::PollingProcessor now stops requestor on shutdown
• Extensive specs added for initializer/synchronizer behavior, header/fallback handling, and payload parsing

^{Written by Cursor Bugbot for commit c5ca138. This will update automatically on new commits. Configure here.}

[keelerm84]

Changes seem okay to me, minus the bot feedback.

[cursor]

HTTP client connections never closed, causing resource leak

Medium Severity

HTTPPollingRequester and HTTPFDv1PollingRequester create persistent HTTP connections via new_http_client (which calls .persistent()) but neither class provides a stop or close method to release these connections. The existing Requestor class follows the pattern of having a stop method that calls @http_client.close. Without cleanup methods, persistent connections holding file descriptors and sockets are never released when the data source is stopped, leading to resource leaks in long-running applications.

Additional Locations (1)

• lib/ldclient-rb/impl/data_system/polling.rb#L294-L310