Allow explicitly marking blueprint parameters as being recipe types -- FIXED, THANKS

[Rockets]

It seems that, in parameterized blueprints, the blueprint "knows" whether each parameter is for a recipe or not. If a parameter is a recipe, you can set other parameters to be derived as ingredients of it, you can use the pN_t and pN_iX variables in formulas, and so on. If a parameter is not a recipe, you can't use these things.

As far as I can tell, whether a parameter is recognized as a recipe comes down to: there must be some machine with that recipe actively set on it at the moment when you update the blueprint's contents. Normally this is fine -- why do you care about recipes that aren't in use? -- but it's a problem when you're using circuits to dynamically set the recipe on the machine. In that situation, your machine only has one (or zero!) of the possible recipes active at the time of blueprinting, so the other parameters in the blueprint aren't recognized as recipes, and you can't use their derived variables.

I'm fine with the current system where it implicitly figures out whether a parameter is a recipe or not as the default behavior, it makes intuitive sense in almost all situations. But it would be nice if there was a checkbox or something to explicitly tag a parameter as being for a recipe even if the blueprint has no machines with that recipe set.