This is currently necessary since Qiskit TOQM isn't published to PyPI
for Linux aarch64 due to a bug.

...when configured using one of its optimization strategies. This is because
non-optimal configurations (i.e. anything using GreedyMapper under the
hood) aren't compatible with the layout search parameter, and in fact
break when it is provided. These configurations happen to always perform
layout (without the explicit search) through a different means. To make
everything consistent, it should be assumed that no matter which optimization
strategy is used, layout changes will be made via routing.

qiskit-toqm users can still create a custom strategy if they wish to use
an optimal configuration that does not make layout changes, and then
use their own pass manager.

This exercises the optimal mapper code paths of qiskit-toqm
opt levels.

…qm-optional

…qm-optional

…qm-optional