record the receptor unit ID on the job record for debugging purposes

[ryanpetrello]

see: #8641

[AlanCoding]

This won't be in the actual job environment, will it?

[AlanCoding]

I think I've confirmed that (via ansible/test-playbooks#153)

My thought was that a new UnifiedJob field would be a less confusing way to present that. Aside from system jobs, workflow jobs, and approval jobs, I think that all job types should have this non-blank.

[ryanpetrello]

@AlanCoding it won't, no. This JSON blob was just a convenient place to store the data without having to resort to a new column on a table that tends to be very large (schema changes on this table tend to be quite expensive).

If you all don't like this approach, that's fine, though. I figured this PR was a cheap way to get us what we needed for debugging.

[softwarefactory-project-zuul]

Build succeeded.

• awx-api-lint : SUCCESS in 2m 25s
• awx-api : SUCCESS in 6m 25s
• awx-ui : SUCCESS in 15m 00s
• awx-swagger : SUCCESS in 7m 38s
• awx-detect-schema-change : SUCCESS in 10m 01s (non-voting)
• awx-ansible-modules : SUCCESS in 4m 25s

[shanemcd]

We will eventually probably need this in its own database column, but I think this is fine for now.

[softwarefactory-project-zuul]

Build succeeded.

• awx-api-lint : SUCCESS in 2m 22s
• awx-api : SUCCESS in 7m 30s
• awx-ui : SUCCESS in 14m 18s
• awx-swagger : SUCCESS in 7m 49s
• awx-detect-schema-change : SUCCESS in 9m 42s (non-voting)
• awx-ansible-modules : SUCCESS in 4m 22s

[softwarefactory-project-zuul]

Build succeeded (gate pipeline).

• awx-api-lint : SUCCESS in 2m 53s
• awx-api : SUCCESS in 7m 13s
• awx-ui : SUCCESS in 15m 06s
• awx-swagger : SUCCESS in 7m 39s
• awx-detect-schema-change : SUCCESS in 7m 09s (non-voting)
• awx-ansible-modules : SUCCESS in 4m 39s
• awx-push-new-schema : SUCCESS in 7m 17s (non-voting)