Evaluate use of FSmeshSwitch to consolidate part variants

[sumghai]

Mesh switching may allow the end taper to be toggled on/off, such that separate tapered and flat-ended module variants in the VAB/SPH parts lists are no longer required.

Assess if this is possible / feasible.

[sumghai]

Initial test involved successfully swapping of the tapered ring and plain bulkhead ring objects on a Karmony Mission Module (the base model used on most module variants). Since FSmeshSwitch could not reference objects from MODEL{} nodes, the tapered ring object had to be duplicated in the Mission Module model itself.

Contrary to Firespitter documentation, FSmeshSwitch was unable to handle multiple objects per variant, which is problematic considering the way the colliders for the recessed tapered end rings were initially configured.

Because it was essential to have these end taper colliders, the ultimate decision was to abandon this particular line of investigation - tapered and flat-ended parts will continue to have separate listings in the VAB/SPH.