Raise warning when user attemps mitigation with local simulator

[ihincks]

What is the expected feature or enhancement?

A user has reported (but I have not confirmed; please tell me if this is wrong) that running in local simulation mode with mitigation turned on silently ignores these options. This might be confusing to users if they expect the noise profile of the simulation to be different when these options are turned on.

The request is to raise a warning in this case.

I expect there are some open questions here: is running with fake backends supposed to completely spoof the runtime execution, like cloud simulators would, and emulate all of the metadata and so forth? Or are they only required to obey the minimum contract of the base primitive classes, and put something in the databin?

[jyu00]

running in local simulation mode with mitigation turned on silently ignores these options.

It should already raise a warning if an unsupported option is used.

[kt474]

Is this asking about mitigation in general or specific options related to mitigation? For example, setting zne_mitigation or measure_mitigation explicitly to True will raise a warning, but setting something like the resilience_level will not.