fix(unit tests): prevent missing components errors for memory tables in tests (#24081)

* fix(unit tests): prevent missing components errors for memory tables in tests

This ensures that memory enrichment tables are always considered in tests, because we can't be sure
if they are used.

Related: #23972

* Add changelog entry

* improve comment

---------

Co-authored-by: Pavlos Rontidis <pavlos.rontidis@gmail.com>

Author: esensar

changelog.d/24081_memory_tables_in_tests.fix.md

@@ -0,0 +1,3 @@
+Fixed an issue in vector tests where memory enrichment tables would report missing components errors.
+
+authors: esensar Quad9DNS

src/config/unit_test/mod.rs

@@ -432,6 +432,15 @@ async fn build_unit_test(
         .collect::<Vec<_>>();
     valid_components.extend(unexpanded_transforms);
 
+    // Enrichment tables consume inputs but are referenced dynamically in VRL transforms
+    // (via get_enrichment_table_record). Since we can't statically analyze VRL usage,
+    // we conservatively include all enrichment table inputs as valid components.
+    config_builder
+        .enrichment_tables
+        .iter()
+        .filter_map(|(key, c)| c.as_sink(key).map(|(_, sink)| sink.inputs))
+        .for_each(|i| valid_components.extend(i.into_iter()));
+
     // Remove all transforms that are not relevant to the current test
     config_builder.transforms = config_builder
         .transforms