Expose deprecatedById in workflowRuns query interface

[j-x-han]

Updates codegen to expose ids of related objects from the same table in the query interface, i.e.:

• On taxa, allow users to query for taxClassId, taxFamilyId, etc.
• On workflowRuns, allow users to query for deprecatedById

Manually tested:

• Update one workflowRun to be deprecatedBy another

• Verify that the deprecatedById is set as expected, and we can query for it

[j-x-han]

I removed these lines because this was causing some unexpected behavior (the actual change is in the codegen template, but this is easier to look at):

• I have two workflowRuns, one ending in 6397d (status ABORTED) and one ending in d80a8 (status CREATED)
• In my update mutation, I'm trying to update 6397d to be deprecated by d80a8
• But after running the mutation, it looks like the reverse has happened, even though the updatedAt timestamp was set on the correct workflowRun

Removing these lines allows us to update the correct workflowRun's deprecatedById value as we expect (see the example in the PR description).

To be completely honest, I'm not sure why these lines were causing the incorrect workflowRun to be updated. I tried stepping through the code and it looked like all the correct objects were being fetched/updated with the right params, so I'm not sure why updating the id instead of the actual related object fixes it.

My best guess is that something funky is going on with the underlying logic because deprecatedBy causes workflowRun to have a 1:1 relationship with itself. Let me know if there are concerns with this change or if there are any other solutions to fix this!

[rzlim08]

LGTM