Implement if/then logic within QueenBee functions

[chriswmackey]

After my initial development of queenbee functions and recipes, I think this was my biggest pain point.

To give a specific painful example, the current philosophy of "create a new function for every boolean flag you want to turn on/off on a command" is causing me to fall far short of the re-usability that we are hoping queenbee will give us. I already have 5 different simulation parameter commands in honeybee-energy and having to make 2 variants of each of them to accommodate one boolean option is already 10 functions. God help us all if I add another boolean flag on these simulation parameter commands and we will have 20 simulation parameter queenbee functions. Simply instituting an if/then logic will allow us to expose these boolean flags on the function rather than having to double or quadruple the number of functions.

Beyond this, there's potentially a lot more re-usability that we can build into queenbee functions if we can wrap multiple commands depending upon the input

[mostaphaRoudsari]

We are holding off on this issue for now until Argo provides better support for conditionals with artifacts.

Meanwhile the logic can be handled inside the functions itself.