Inconsistency with Cirq for pulling back existing job results from different providers

Consistent behavior for service.run() job

When using service.run(), we see that the resulting output is consistent across providers:

IonQ

Honeywell

Calling service.run against different providers both return a CirqResult.

Inconsistent behavior for job.results() of existing job

However, when pulling back an existing job, we see inconsistent behavior:

For IonQ and Honeywell, job.results() returns the Raw Result format from the provider, rather than a consistent microsoft Result format that contains counts/probabilities.

In addition, it does not seem possible to get existing jobs back into the same format as if I were calling service.run(). For IonQ, I can use to_cirq_result to get back the result similar to when I called service.run().

If trying the same thing for honeywell, I get an error that dict object has no attribute to_cirq_result:

This means that even though honeywell service.run() returned a CirqResult, it is not possible to use similar method to get out a CirqResult from an existing job.

Reproduce the reported behavior by comparing service.run() with results from an existing job for IonQ and Honeywell. Inspect the returned result types and the available conversion methods, then make both providers expose a consistent result format and verify that an existing Honeywell job can be converted to a CirqResult like an IonQ job.