Add derivation defintions and values to OpenMCT plugin

Issue: OpenMCT plugin only sends a packet's fields, but not its derivations.

Fix: Update OpenMct to include derivations in both

1. the telemetry dictionary definition
2. a packet instance

More details:

1. Update the section that converts to the telemetry dictionary into an OpenMCT JSON structure
   https://github.com/NASA-AMMOS/AIT-Core/blob/184d8bec62c274627ffd1bc488f4e70555caf8e7/ait/core/server/plugins/openmct.py#L215

I suspect there is enough commonality between fields and derivation objects (name, units, type) that you could just add another loop that iterates over a packet-def’s derivationmap, almost a parallel of what it does for fieldmap:
https://github.com/NASA-AMMOS/AIT-Core/blob/184d8bec62c274627ffd1bc488f4e70555caf8e7/ait/core/server/plugins/openmct.py#L226

2. Update the section that converts a telemetry packet
   https://github.com/NASA-AMMOS/AIT-Core/blob/184d8bec62c274627ffd1bc488f4e70555caf8e7/ait/core/server/plugins/openmct.py#L207

Similar to part 1, add a second loop the parallels fieldmap but for derivationmap.

Start in ait/core/server/plugins/openmct.py at the telemetry packet conversion around line 207 and the telemetry dictionary conversion around line 215. Read the existing fieldmap loops and inspect the packet definition's derivationmap. Done means derivation definitions appear in the OpenMCT telemetry dictionary and derivation values appear in each converted packet instance.