Petascope should not import coverage which contains "-" as coverage id

[Bang Pham Huu]

a valid rasdaman collection cannot contain "-" so in Petascope, it replaces "-" with "_" implicitly when handling InsertCoverage, UpdateCoverage.

As WCPS does not support "-" for coverageId, then any requests with this kind of coverage will return error by parsing.

for c in (test_mr1-1) return encode(c, "csv")

A parsing error occurred at position=1:18. Offending symbol is=[@5,18:18='-',<51>,1:18]. Parser message=mismatched input '-' expecting {',', RETURN, ')', WHERE}.

so Petascope InsertCoverage,UpdateCoverage shouldn't replace "-" with "_" and should throw exception.