Investigate FlowCapableNodeConnectorStatistics building

There seems to be a code path where the metrics are gathered without bytes and packet metrics.  The FlowCapableNodeConnectorStatistics instance is not padded out to accomodate this missing data and downstream processing is expecting the data or padded data to be there and fails when it is not.   This is fixed at one downstream point in TSDR-52 but there may be other downstream points where this can fail.  OR all downstream points should check for the missing data before allocating a TSDRMetricsRecord container.