Don't store circuit params automatically

[kt474]

Summary

Details and comments

Fixes #987

[coveralls]

Pull Request Test Coverage Report for Build 5954209661

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage remained the same at 74.058%

---

Files with Coverage Reduction	New Missed Lines	%
qiskit_ibm_runtime/qiskit_runtime_service.py	2	81.37%

Totals
Change from base Build 5953027740:	0.0%
Covered Lines:	2458
Relevant Lines:	3319

---

💛 - Coveralls

[merav-aharoni]

LGTM.
Two questions just for my understanding -

1. Why did you add the kwargs parameter and not keep params or simply remove both?
   And why not remove the params in the creation of the RuntimeJob in QiskitRuntimeService?
2. Why did you modify the SerializableClass.__eq__ method?

[kt474]

1. Why did you add the kwargs parameter and not keep params or simply remove both?
   And why not remove the params in the creation of the RuntimeJob in QiskitRuntimeService?
2. Why did you modify the SerializableClass.__eq__ method?

You are right, removing params in the creation of the runtime job here is a much better approach - I was a bit backwards here (fixed). Since the params are no longer automatically a part of the runtime job, this custom serialization class returns {'value': 'foo'} which needs to be deserialized