retain CTD deployment comments in event log output

[sbeaulieu]

comments from original elog file not provided to REST API end user in present CTD deploy workflow. example see README for ar34a events API

[joefutrelle]

@sbeaulieu here's the README, can you explain how it's relevant to this issue?

2022-08-09 (_edit2 file) Removed the 2 Message ID with CTD911 other. The _edit2 file has the comments from those 2 Message ID moved into respective CTD deploy.
2022-08-09 (_edit file) Noticed there is a blank in the dateTime8601 column, Message ID 36. Filled with "Date" in appropriate format because there are no Revisions.
2019-08-20 (original file) NES-LTER Info Manager does not know why the API is not working for this elog

[sbeaulieu]

Actually we should revise this issue into 2 issues: not only to retain the comments field for events with CTD "deploy", but also to retain entire row with CTD "other" in event log output. If we retained the latter, then I would not have tried the manual _edit2 file in previous comment. The goal in both of these cases is to retain comments with regard to CTD operations that are noted into the event log.

[joefutrelle]

We're removing CTD events and generating new deploy events from .hdr files. So we should be doing one or the other: 1) retaining CTD deploy events and their metadata, or 2) removing and regenerating CTD deploy events (the current approach).

We can't do both.

[joefutrelle]

We have the option of not replacing the CTD deployment events.