Command history inplace updates

[shefalijoshi]

Closes #315

Describe your changes:

Rather than create a new view provider and view for command history in openmct-yamcs, added a configuration that indicates that datum for a given object should be updated in place.
Added a unique id for datum that should be aggregated called messageId. This will be used by open mct to update data in place for that message/record.

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Is this change backwards compatible? For example, developers won't need to change how they are calling the API or how they've extended core plugins such as Tables or Plots.

Author Checklist

• Changes address original issue?
• Tests included and/or updated with changes?
• Command line build passes?
• Has this been smoke tested?
• Testing instructions included in associated issue OR is this a dependency/testcase change?

Reviewer Checklist

• Changes appear to address issue?
• Reviewer has tested changes by following the provided instructions?
• Changes appear not to be breaking changes?
• Appropriate automated tests included?
• Code style and in-line documentation are appropriate?
• Has associated issue been labelled unverified? (only applicable if this PR closes the issue)
• Has associated issue been labelled bug? (only applicable if this PR is for a bug fix)

[ozyx]

Stumbled upon a mistaken version update

[akhenry]

Looks good, thanks. Some small changes suggested on nasa/openmct#6694 (comment) which has implications for this PR.