Expose source of stand assignment in API #1745
Description
As discussed in #sector-file-development on Discord; would require Plugin changes
At least whether the assignment is the result of a pilot request should be exposed in the relevant stand routes, but would welcome comment on this matter (would a boolean "was assigned by reservation allocator" suffice, or should the specific allocator class be published?)
Given the structure of these responses, adding these in a backwards-compatible manner (as an additional JSON key) should be possible