Don't refresh the job as soon as we receive the result.

[dstrain115]

• Currently, each streaming result refreshes the result.
• This refresh is only needed to get the job finished time, which is not really used anywhere.
• Forgoing this can reduce batch result times by ~200ms per batch item, which can be about a 3x for small circuits.
• This PR makes the job_finished_time optional and does not populate it.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.37%. Comparing base (dbde273) to head (ee4290a).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7662      +/-   ##
==========================================
- Coverage   99.37%   99.37%   -0.01%     
==========================================
  Files        1082     1082              
  Lines       96700    96689      -11     
==========================================
- Hits        96097    96085      -12     
- Misses        603      604       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[wcourtney]

This resource seems to map to a QuantumResult API resource, but the class doesn't contain the unique identifier for that resource - job_id is only unique within a QuantumProgram parent, which is only unique within a GCP project.

[dstrain115]

Well, that's a pre-existing issue, but I could add more fields while I am here. What else should we add, if anything?

[wcourtney]

project_id and program_id should be included as well and match the values in the parent EngineJob. Feel free to leave as a followup or file a bug since it's out of scope of this change if you aren't going to lazy load the timestamp of the job's completion.

[dstrain115]

Yeah, I will do that in a follow-up.

[wcourtney]

Is this used anywhere besides tests and places working around the requirement to set the field? Could we just remove it?

[dstrain115]

Totally removed.

[wcourtney]

project_id and program_id should be included as well and match the values in the parent EngineJob. Feel free to leave as a followup or file a bug since it's out of scope of this change if you aren't going to lazy load the timestamp of the job's completion.