Lead bind address ends up in the wrong place

[mfeit-internet2]

Wayne Jackson at NASA dropped me a line with a pSConfig file containing the following:

"foo.bar.org": {
      "_meta": {
        "display-name": "Foo"
      },
      "address": "foo.bar.org",
      "lead-bind-address": "1.2.3.4",
      "host": "foo"
    }

He found this in the logs, which has the lead bind address mis-named and in the wrong place for pScheduler to be able to use it:

2025-02-21 19:22:53 INFO guid=... action=create checksum=... lead_url=https://foo.bar.org/pscheduler test_type=throughput task={
    "test": {
        "spec": { ... },
        "type": "throughput"
    },
    "schedule": { ... },
    "reference": {
        "source_lead_bind_address": "1.2.3.4",
        "psconfig": { ... },
    },
    "tools": ["iperf3", "nuttcp"]
}

The parameter should be this, at the same level as test and schedule, for pScheduler to bind to it:

task={
    ...
    "lead-bind": "1.2.3.4",
    "test": { ... },
    ...
}