Comment 14 for bug 1963707

Thank you Sebastien
to help others not reading or diffing it that means in regard to
- https://github.com/canonical/ubuntu-mir/issues/30
- https://github.com/canonical/ubuntu-mir/pull/31

You have added
"""
We believe we have exercised the different options available to provide testing without managing to find a solution.
We will keep trying to resolve the testing gap but meanwhile we would still like to request for the package to be consider because we can't provide the feature as an opt-in/in universe since it's a build option from modemmanager but not an independent plugin.
Due to the nature, integration and use cases of the package the consequences of a regression that might slip through most likely would be that Qualcomm modems stop working correctly.
"""

To wich with the new ruling we'd answer
"""
This does need special HW for thorough testing, but all options to
get this covered have been exhausted and based on demonstration of
enough investigation and proof of why there is currently no other
option it is accepted as-is as a compromise.
The owning team is committed and aware of the implications for
ongoing maintenance.
"""

Thereby the former back and forth on the testing is resolved (not by having it, but by accepting to be unable to do so for now).

Thereby all open required TODOs are fulfilled and this can be promoted.
As it is not yet showing as component mismatch I'm setting "In Progress" state for now.
Feel free to ping back when this is trying to be pulled in, we should also see it on the MIR team meetings check of mismatches then.