[2.0.13] "Set recipe" matching outputs leads to confusing results

[ExtraTricky]

What happened to me:
1. Connect an asteroid crusher to a circuit and check "set recipe".
2. Output a "metallic asteroid chunk" signal to the circuit.
3. Observe that the crusher sets the recipe to Metallic asteroid crushing.

After replicating this in the editor, I realized that this is happening because "set recipe" is not just matching the recipe signals, but also matches recipes that contain the signal in their output. So since Metallic asteroid crushing has metallic asteroid chunk in its outputs, it gets chosen as the recipe based on the "metallic asteroid chunk" signal.

What I would expect:
Recipe is only set based on signals that are recipes, so a "metallic asteroid chunk" signal would not cause any recipe to be set.

I've attached a quick editor-made save file that shows some examples.

Now that I understand how this works, I could see an argument that it's not exactly a bug. However, I definitely thought it was a bug when my "set recipe" crushers started making iron ore when I never set a crushing recipe anywhere on the circuit! (I was running the same circuit to a "set filter" inserter and started outputting the chunk signals for that filter).

[Rseding91]

Thanks for the report. This is not a bug.