Fix Steep failures from over-tight type-fill + reinstate scheduler_loop ignore

CI's Steep run flagged 10 errors after the previous "fill in concrete types"
commit. Two type-fill changes were too tight, and one steep:ignore removal
was unverified locally because libdatadog version mismatch blocked Steep
here at the time. CI surfaced all three.

1. Component @logger / initialize logger / environment_supported? logger:
   revert to `untyped`. The tightened `SymbolDatabase::Logger` type didn't
   match Uploader's `Datadog::Core::Logger` parameter type, surfacing a
   long-standing inconsistency between the SymDB Logger wrapper and the
   downstream component sig declarations. Reverting to `untyped` matches
   the established cross-component logger-handoff convention (see DI's
   sigs for the same pattern); fixing the underlying inconsistency in
   Uploader / Extractor / ScopeBatcher sigs is out of scope for this PR.

2. Remote process_change `change` and receiver block's `changes`: revert
   to `untyped`. The union type
   `Repository::Change::Deleted | ::Inserted | ::Updated` looked right but
   Steep cannot narrow the union by the `case change.type` dispatch the
   code uses — `.content` exists only on Inserted/Updated, `.previous`
   only on Deleted/Updated, so every access through the union flagged.
   The runtime dispatch via `.type` symbol matches what the code does
   correctly; reverting to `untyped` matches the pattern. (DI's
   remote.rbs takes the same approach.)

3. scheduler_loop in component.rb:306: reinstate a per-line
   `# steep:ignore NoMethod` on the `@scheduled_at - Time.get_time`
   line, with an inline comment explaining that Steep does not narrow
   nullable instance variables across an `if @scheduled_at.nil?`
   check. Per-line rather than the previously removed block-level
   ignore — only one line needs suppression.

Verification:
- bundle exec steep check → No type error detected. (locally, with
  libdatadog 33.0.0.1.0 now installed)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: p-ddsign

lib/datadog/symbol_database/component.rb

@@ -303,7 +303,11 @@ def scheduler_loop
               @scheduler_signaled = false
               @scheduler_cv.wait(@scheduler_mutex)
             else
-              remaining = @scheduled_at - Datadog::Core::Utils::Time.get_time
+              # steep:ignore NoMethod — Steep does not narrow @scheduled_at from `Float?`
+              # to `Float` across the `if @scheduled_at.nil?` check above (instance-variable
+              # narrowing is not tracked). Runtime is safe: the else branch only runs when
+              # the variable is non-nil.
+              remaining = @scheduled_at - Datadog::Core::Utils::Time.get_time # steep:ignore NoMethod
               if remaining > 0
                 # Wait until the debounce deadline. Any signal (start_upload,
                 # stop_upload, shutdown!) wakes us early; we always re-loop

sig/datadog/symbol_database/component.rbs

@@ -15,7 +15,7 @@ module Datadog
 
       @settings: Datadog::Core::Configuration::Settings
       @agent_settings: Datadog::Core::Configuration::AgentSettings
-      @logger: SymbolDatabase::Logger
+      @logger: untyped
       @extractor: Extractor
       @uploader: Uploader
       @scope_batcher: ScopeBatcher
@@ -33,7 +33,7 @@ module Datadog
 
       def self.build: (Datadog::Core::Configuration::Settings settings, Datadog::Core::Configuration::AgentSettings agent_settings, untyped logger) -> Component?
 
-      def initialize: (Datadog::Core::Configuration::Settings settings, Datadog::Core::Configuration::AgentSettings agent_settings, SymbolDatabase::Logger logger) -> void
+      def initialize: (Datadog::Core::Configuration::Settings settings, Datadog::Core::Configuration::AgentSettings agent_settings, untyped logger) -> void
 
       attr_reader settings: Datadog::Core::Configuration::Settings
       attr_reader last_upload_time: Time?
@@ -54,7 +54,7 @@ module Datadog
 
       private
 
-      def self.environment_supported?: (SymbolDatabase::Logger logger) -> bool
+      def self.environment_supported?: (untyped logger) -> bool
 
       def ensure_scheduler_thread: () -> void
 

sig/datadog/symbol_database/remote.rbs

@@ -9,9 +9,9 @@ module Datadog
 
       def self.receivers: (Datadog::Core::Telemetry::Component telemetry) -> Array[Core::Remote::Dispatcher::Receiver]
 
-      def self.receiver: (?Array[String] products) { (Datadog::Core::Remote::Configuration::Repository repository, Array[Datadog::Core::Remote::Configuration::Repository::change] changes) -> void } -> Array[Core::Remote::Dispatcher::Receiver]
+      def self.receiver: (?Array[String] products) { (Datadog::Core::Remote::Configuration::Repository repository, ::Array[untyped] changes) -> void } -> Array[Core::Remote::Dispatcher::Receiver]
 
-      def self.process_change: (Component component, Datadog::Core::Remote::Configuration::Repository::change change) -> void
+      def self.process_change: (Component component, untyped change) -> void
 
       def self.enable_upload: (Component component, Datadog::Core::Remote::Configuration::Content content) -> void