ParameterVector support for pulse parameter assignment

[arthurostrauss]

Summary

This PR proposes an extended use of the current method assign_parameters in the ParameterManagerto enable the assignment of a list of values through ParameterVectorclass. This enables an extended usage for the same methods in the Scheduleand ScheduleBlockobjects.

Details and comments

The PR simply takes the already existing unrolling method from QuantumCircuitand applies it for the pulse level case, to enable a simple extension of the existing methods for parameter assignment.
This can be practical when mixing pulse level calibrations with many parameters.
This PR closes #5233

[qiskit-bot]

Thank you for opening a new pull request.

Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient.

While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone.

One or more of the the following people are requested to review this:

• @Qiskit/terra-core
• @nkanazawa1989

[arthurostrauss]

This PR would solve issue #5233

[coveralls]

Pull Request Test Coverage Report for Build 8398804079

Details

• 16 of 19 (84.21%) changed or added relevant lines in 2 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.03%) to 89.33%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
qiskit/pulse/parameter_manager.py	14	17	82.35%

Files with Coverage Reduction	New Missed Lines	%
crates/qasm2/src/lex.rs	1	92.62%

Totals
Change from base Build 8391327735:	0.03%
Covered Lines:	59811
Relevant Lines:	66955

---

💛 - Coveralls

[wshanks]

This looks great! I had some feedback on the documentation, but the code looks fine.

[TsafrirA]

Looks good to me. Just a minor typo and perhaps an extra test.

[TsafrirA]

Thanks @arthurostrauss for the final fixes! This looks great.
@nkanazawa1989 - Why commits from other PRs are marked as differences here?

[wshanks]

I think GitHub is confused about the multiple branches/merges. When I look at the diff locally (like git checkout -b tmp Qiskit/main and git merge --squash arthurostrauss/ParameterVector_pulse), it looks right.

[wshanks]

@arthurostrauss This looks good to me now! Do you want to try to make it look clean in GitHub, so we know it will merge the way we want? I can squash things down and force push to your branch if you want.

[arthurostrauss]

@arthurostrauss This looks good to me now! Do you want to try to make it look clean in GitHub, so we know it will merge the way we want? I can squash things down and force push to your branch if you want.

@wshanks Yes if you can do such force push (if necessary) I'd be happy to let you do it, as I'm not sure how to proceed on my side for this.

[wshanks]

@arthurostrauss Actually, the diff looks good in GitHub now after the last merge, so I think it is fine to merge as is. I am not sure what messed up the diff view before.