Library name does not conform to CSM API

[jessemapel]

From section 5.5 of the 3.0.3 API:

The name of a CSM library must uniquely identify it. It shall be named by concatenating the platform name or abbreviation (e.g. GLOBAL_HAWK_RQ4A), the specific sensing device identifier (e.g. SAR), the development contractor name (e.g., HARRIS), the version release number (see 5.9.20 Plugin::getModelVersion), the computing platform operating system (e.g. Solaris10), a CSM version number followed by a decimal point and the appropriate extension (e.g. dll, so).

So our library could be:

Planetary_Generic_USGSASC_LinuxX86_csm3_0_3.so/dll/dylib

It's not particularly clear what we should put for some of these because our model is for multiple platforms and sensor types. I'm also not sure how we can set library name based on the build platform, seems very against Conda build norms.

[scsides]

It's not truly "generic", maybe something like "multiple". May be a small argument for breaking it up into one library for each sensor type.

Skipped the "version release number"?

[jessemapel]

Yeah, so maybe:

Planetary_Multiple_USGSASC_1_0_0_LinuxX86_csm3_0_3.so/dll/dylib