Disable LiDAR in IfW at FAST.Farm level

[andrew-platt]

Ready to merge

Feature or improvement description
The LiDAR sub-module inside InflowWind requires turbine specific information such as hub location. However, this information is not available at the FAST.Farm level instance of InflowWind. This was resulting in segmentation faults when someone attempted to use it at this level.

This PR disables the LiDAR submodule from use with the InflowWind module used at the FAST.Farm level.

Related issue, if one exists
#2316
#2324

Impacted areas of the software
InflowWind module at the FAST.Farm level only.

Additional supporting information
A few users have attempted to use the LiDAR sub-module at the FAST.Farm level and received segmentation faults. Since this is not something the code can really do, we are simply disabling it for now.

Test results, if applicable
No results change.

[deslaughter]

I probably would have reversed the logic and done LidarEnable = .true. in the registry file and set it to .false. where it's initialized in FAST.Farm. Otherwise, the flag will have to be set to false to achieve normal operation. For example, does this flag need to be set false in the ADI library or the InflowWind C Bindings?

[andrew-platt]

At present the Lidar doesn't output anything to file, but simply populates data to pass to the controller. In the ADI library and InflowWind c-bindings library, there are no provisions for a controller so Lidar shouldn't be used there.

I can change the logic on that, but I do thing we should default it to disabled.