MET Couchbase document ID - implement sequential numeric/GUID based ID

[gopa-noaa]

Current ID scheme concatenates header fields, and given how the header columns are allocated in MySQL schema, there is a possibility that we will run over the Couchbase 250 length limit on ID. Based on team discussion, we are currently switching to a numeric/GUID. Need to research the best way to implement this.

[gopa-noaa]

We decided to stay with @randytpierce scheme of algorithmic text ID for now, but there are hooks in place in METdatacb to fall back to GUID

[ian-noaa]

For now, it doesn't seem like we'll need this so moving to the backlog until it becomes an issue.