Slight improvements to Qiskit Runtime retry loop

[garrison]

I made a few slight improvements to the Qiskit Runtime retry loop.

• use for/else to simplify for loop logic, following my earlier comment at Support options forging #47 (comment)
• add job id to warning message
• use a named logger

Most importantly, I ran this code and actually witnessed it do the retry loop and then continue successfully.

[coveralls]

Pull Request Test Coverage Report for Build 3395042552

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 1 of 5 (20.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.06%) to 84.769%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
circuit_knitting_toolbox/entanglement_forging/entanglement_forging_knitter.py	1	5	20.0%

Totals
Change from base Build 3394967266:	0.06%
Covered Lines:	1525
Relevant Lines:	1799

---

💛 - Coveralls