jobs_directory breaks version checking

The Galaxy Pulsar runner has a version check that ensures the remote Pulsar is running a supported version. This is done by checking the value of `pulsar_version` in the job config dict returned by the job setup call in the Pulsar client.

With `jobs_directory` set, this remote Pulsar query is short circuited and the job config is created on the Galaxy side. In this case `pulsar_version` is set to the version of the Pulsar client library in Galaxy, so the check is comparing against the wrong version.

Start by tracing the Galaxy Pulsar runner's job setup and version-check path, then compare behavior with and without `jobs_directory` enabled. Verify that the check uses the remote Pulsar version rather than the Galaxy-side client version, and confirm the supported-version check still rejects incompatible remote Pulsar instances.

Written by the indexing model from the issue text.