What is the expected feature or enhancement?

QiskitRuntimeLocalService was created to support local testing mode and is meant to be similar to QiskitRuntimeService. The initial release of QiskitRuntimeLocalService only has the run() method, and we immediately got feedback asking for the other methods 🙂.

This issue is about adding job related methods to QiskitRuntimeLocalService. This is more involved since job data (e.g. results) would need to be stored locally on disk. So to support this, we'd need a design on

1. Where to store the data. This should be user-configurable and the default can be current working directory.
2. When to delete the data. This should be user-configurable and the default can be 30 days.
3. Job id to data file mapping. For fast query (jobs() call), we probably want to also store job metadata, such as backend name, in a structured way.

Acceptance criteria

Add the following methods to QiskitRuntimeLocalService

• job
• jobs
• delete_job