Remove deprecation warning for unsupported parameters of transpilation settings

[merav-aharoni]

Summary

Removed 1 deprecation warning for unsupported parameters of transpilation settings.

Details and comments

Part of #784 .
Question - regarding translation_method and timing_constraints, do we want to raise an error or simply ignore? Because for other unsupported options, we simply ignore.

[coveralls]

Pull Request Test Coverage Report for Build 5104060843

• 24 of 24 (100.0%) changed or added relevant lines in 5 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.2%) to 72.73%

---

Totals
Change from base Build 5082986167:	0.2%
Covered Lines:	2587
Relevant Lines:	3557

---

💛 - Coveralls

[kt474]

Question - regarding translation_method and timing_constraints, do we want to raise an error or simply ignore? Because for other unsupported options, we simply ignore.

Since it's been more than 6 months, I think we can just ignore unsupported options

[merav-aharoni]

When checking the removal of deprecation warning, I noticed that if an unsupported option is passed, the server will return an error (possibly after a long time). So I added validation checks for level 2 options. We already have checks for level 1 and level 3.

[jyu00]

We specifically allow kwargs in Options to let people test undocumented features. That's why these dataclasses are decorated with @_flexible. If you are going to raise, perhaps one can bypass the validation with an env variable (I think there was one before, but maybe it's in qiskit-ibm-provider).

[merav-aharoni]

@jyu00 - Indeed there is an environment variable that controls whether to run _validate_options or not. So the user can turn set QISKIT_RUNTIME_SKIP_OPTIONS_VALIDATION=False to turn off all the validations.