Feature request: Allow user to change turbine model dynamically

[misi9170]

Current behavior

To change turbine models, and specifically, user-provided turbine yaml files that are not located in turbine_library/ but are instead !included in the FLORIS input yaml, users currently need to specify a second FLORIS input file. A good example of this is the FLORIS input files currently in examples/floating_inputs, where several FLORIS models exist that are identical except for the turbine model they call.

Desired behavior

To declutter the examples and provide users a simpler way of switching between turbine models, I'd like there to be an option of changing the turbine model of a FlorisInput object exported to a dictionary, so that a viable workflow would be:

fi_turb1 = FlorisInterface('example_floris_model_with_bang_included_turbine_model_1.yaml')
fi_dict = fi_turb1.floris.as_dict()
<code to change the bang-included turbine to turbine_model_2>
fi_turb2 = FlorisInterface(fi_dict)

As well as allowing us to clean up the examples, this also helps prevent growth in the number of needed examples and challenges/bugs associated with changing the examples. I could also imagine it becoming more important with turbines defined with multi CpCt tables.

[misi9170]

#729 May help with this