processor information is missing in json reports

From Jeff's bug on hexr,

https://certification.canonical.com/hardware/201907-27213/submission/147411/

dmidecode has:

Processor Information
 Socket Designation: CPU01
 Type: Central Processor
 Family: ARM
 Manufacturer: Hisilicon
 ID: 10 D0 1F 48 00 00 00 00
 Signature: Implementor 0x48, Variant 0x1, Architecture 15, Part 0xd01, Revision 0
 Version: Hisilicon 1620
 Voltage: 0.9 V
 External Clock: 100 MHz
 Max Speed: 2600 MHz
 Current Speed: 2600 MHz
 Status: Populated, Enabled
 Upgrade: Unknown
 L1 Cache Handle: 0x0023
 L2 Cache Handle: 0x0024
 L3 Cache Handle: 0x0025
 Serial Number: To be filled by O.E.M.
 Asset Tag: To be filled by O.E.M.
 Part Number: To be filled by O.E.M.
 Core Count: 64
 Core Enabled: 64
 Thread Count: 64
 Characteristics:
  64-bit capable
  Multi-Core
  Execute Protection
  Enhanced Virtualization
  Power/Performance Control

submission.json has

    "processor": {
        "bogomips": "200",
        "cache": "-1",
        "count": "128",
        "model": "aarch64",
        "model_number": "0x1",
        "model_revision": "0",
        "model_version": "8",
        "other": "fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma dcpop asimddp",
        "platform": "aarch64",
        "speed": "2600",
        "type": "aarch64"
    },

Jeff linked to an old submission https://certification.canonical.com/hardware/201812-26732/submission/135998/ that has the data from dmidecode in the parsed json. We generated the json from the old checkbox library. In the json that was generated from the old checkbox support tools, it has both the processor element and an element in the devices list that is categorized as PROCESSOR. I pasted the old example up above when I opened hte bug.

basically we need the version information from dmidecode with the processor information, i.e. Version: Hisilicon 1620.

Here is a dump of data from dmidecode.DmidecodeParser using the DmiResult class from there. I would like if this data could be included in the submission.json, though I am uncertain where to go to add it.

(I do not mean for the data to be shaped the same way, the dump is just an example of the content that the parser can generate that includes processor info.)

Considering that the submission.json has the raw dmidecode attachment, I could have c3 use the dmidecode parser from checkbox_support since we have that as a dependency already.