Integrate cable/road-path planning to BOS calculations

[cfrontin]

in #49, we will have brought in a collection system optimization tool. this will take the design above and beyond the BOS capabilities in vanilla LandBOSSE and ORBIT. We should:

• augment the LandBOSSE interface to (optionally) take a custom cable and road path based on the interarray results
• augment the ORBIT interface to (optionally) take a custom cable path based on the interarray results

[cfrontin]

Looking at LandBOSSE, there are three files, all under WISDEM/wisdem/landbosse/model, where spacing is used to determine a BOS cost:

• WISDEM/wisdem/landbosse/model/CollectionCost.py
  • determining section length between turbines
  • determining interconnect/substation location
• WISDEM/wisdem/landbosse/model/ErectionCost.py
  • determining crain transit time between turbines
• WISDEM/wisdem/landbosse/model/SitePreparationCost.py
  • determining road length

I think the best path forward for LandBOSSE is to have the collection system designer create an "effective equivalent spacing" that gives a best-guess of the costs. It's far from optimal, but I think can highlight the point of doing a modular system...

[cfrontin]

@jaredthomas68 bringing in LandBOSSE aspect in #80.