Aborting with a reason does not set the 'reason' field of stop document

Running a scan, then aborting it (via the CLI) with a reason, eg `blueapi controller abort 'Reason for aborting'`, aborts the task as expected but the emitted stop document has `"exit_status":"abort","reason":""`.

Is blueapi not passing it through or is the run_engine not propagating it to the run correctly.

Or is this not the intended purpose of the abort reason and the two are not related?