CMS forces longitude in releaseFile to [0, 360] range

[milancurcic]

After reading the input data in releaseFile, CMS forces the input longitude to be in the [0, 360] range.

https://github.com/beatrixparis/connectivity-modeling-system/blob/fb491389261e895379f9f1bc943e46d66ab59684/cms-master/src/input.f90#L291-L297

However, the input data may be, say, in [-180, 180] longitude range, for example HYCOM GOMb0.01, and we can specify xstart and xend in nest_1.nml.

Is this range change necessary for some logic elsewhere in CMS? If not, we should remove this code as it needlessly complicates working with various model data.