fix(worker): bug-1569 periodic resval reports tagged with wrong host

collect_load_indices() (resource_sync.c) tagged every periodic
mem/r1m/r15m/r15s/ut/pg/ls/it/swp/io/tmp report with gethostname()'s
raw OS/container hostname instead of the worker's own join identity
(xcecd_ctx.virtual_name, the -n/--name value). Every other worker-keyed
lookup downstream (scheduler's sched_get_worker(), and the same
HOOK_DETAIL_RESOURCE_UPDATE payload forwarded on to the Go apiserver)
matches by that join identity, so the mismatch silently dropped every
periodic resource report for the real worker.

Also adds a startup INFO log (main.c) naming the resolved job picker
plugin, used to rule out a legacy-picker hypothesis while chasing a
related (still-open) dispatch issue.

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

src/worker/testsuite/meson.build

@@ -26,6 +26,21 @@ test('worker controller_connector test', controller_connector_test,
     timeout: 60,
     env: ['ASAN_OPTIONS=detect_leaks=0'])
 
+# bug-1569: collect_load_indices() (resource_sync.c) must tag every periodic
+# resource report with xcecd_ctx.virtual_name (the worker's own join
+# identity), not gethostname()'s raw OS/container hostname -- see
+# test_resource_sync.c's own header comment for the full mechanism trace.
+resource_sync_test = executable('resource_sync_test',
+                                'test_resource_sync.c',
+                                include_directories: [worker_test_incdir],
+                                dependencies: worker_test_deps,
+                                install: false)
+
+test('worker resource_sync test', resource_sync_test,
+    suite: 'worker',
+    timeout: 60,
+    env: ['ASAN_OPTIONS=detect_leaks=0'])
+
 # component-failover-adoption task 2.2: worker startup-ordering white-box
 # test. #include's xcecd.c directly (same technique as controller_connector_
 # test above, but a separate binary/file -- xcecd.c and controller_connector.c