Fixes #857

This is an attempt to handle a situation where we need to create an ID for a job. Before this PR:

• createJob() is called
• we generate a UUID and create a job
• the API processes the request and creates a job in the background
• the API call flakes and returns an error
• our auto-retry logic attempts the request again
• the API call falls with a 409: Already Exists error
• we return the 409 to the user

This PR will make it so that when the request is "auto-retried" and returns the 409, we'll ignore it, and instead refresh the metadata of the Job, treating that as if it was the original response from the create request.

• createJob() is called
• we generate a UUID and create a job
• the API processes the request and creates a job in the background
• the API call flakes and returns an error
• our auto-retry logic attempts the request again
• the API call falls with a 409: Already Exists error
• we return the 409 to the user refresh the metadata from the Job and return it to the user

To Dos

• Unit tests