fix(ci): fix Pulsar TLS integration tests with latest image (#25099)

* fix(ci): pin Pulsar integration test image to 4.1.3

The `apachepulsar/pulsar:latest` image moved to a version that breaks
TLS connectivity, causing `pulsar_happy_tls` and
`consumes_event_with_tls` to fail consistently in CI.

Pin to 4.1.3 to unblock the merge queue. Re-enabling `latest` is
tracked in #25096.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Add PULSAR_PREFIX_advertisedAddress=pulsar

* fix(ci): revert Pulsar image pin to latest

* Revert to version: latest

* Fix test.yml format

* Delete obsolete comment

---------

Co-authored-by: Pavlos Rontidis <pavlos.rontidis@gmail.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: 3 people

tests/integration/pulsar/config/compose.yaml

@@ -8,6 +8,10 @@ services:
       - 6650:6650
       - 6651:6651
     environment:
+      # Since apache/pulsar#25238, standalone mode advertises the container's FQDN
+      # (the container ID) instead of localhost. Set explicitly so TLS hostname
+      # verification matches the certificate's DNS SAN.
+      - PULSAR_PREFIX_advertisedAddress=pulsar
       - PULSAR_PREFIX_brokerServicePortTls=6651
       - PULSAR_PREFIX_tlsKeyFilePath=/etc/pulsar/certs/pulsar.key.pem
       - PULSAR_PREFIX_tlsCertificateFilePath=/etc/pulsar/certs/pulsar.cert.pem

tests/integration/pulsar/config/test.yaml

@@ -7,9 +7,7 @@ env:
   PULSAR_HOST: pulsar
 
 matrix:
-  # TODO: re-enable `latest` once TLS tests pass with newer Pulsar images.
-  # See https://github.com/vectordotdev/vector/issues/25096
-  version: ["4.1.3"]
+  version: [latest]
 
 # changes to these files/paths will invoke the integration test in CI
 # expressions are evaluated using https://github.com/micromatch/picomatch