Add test for unreleased Qiskit

[doichanj]

Summary

This PR is preparation for unreleased Qiskit to implement changes and remove deprecations (#1941 )

Details and comments

New test case unit-tests-latest-qiskit-terra is used to detect changes in the latest Qiskit and if any deprecation error found, this PR should be updated

Change logs:
bind_parameters is replaced with assign_parameters
QuantumCircuit.i() is replaced with QunatumCircuit.i() by PR #1945

[mtreinish]

This is a great idea, we had this coverage in the past where tests ran with terra main on each job. But blocking PRs on terra main was a bit too disruptive at the time (just from a dependency management PoV). So adding a dedicated job back to ensure we have some coverage of upcoming changes to terra is a good idea, especially if we do it in a non-blocking manner. The open question I have is mostly about the long term strategy for how/when we run this job.

[mtreinish]

Are you thinking we should run this on every commit? Or was the eventual plan to run this job periodically when it's no longer a WIP? We can set this up in a new workflow file and create a nightly cron job to run this test if we want to do it periodically, see: https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule

[doichanj]

I want to use this test case for testing deprecations and changes of Qiskit. I will remove this test case and only merge fixes in this PR.

[1ucian0]

The open question I have is mostly about the long term strategy for how/when we run this job.

Other components run it daily:

• qiskit-ibm-provider: https://github.com/Qiskit/qiskit-ibm-provider/actions/workflows/unit-tests-terra-main.yml
• qiskit-ibm-runtime: https://github.com/Qiskit/qiskit-ibm-runtime/actions/workflows/unit-tests-terra-main.yml