tree c61c69bcfbf86271d5184a96e59c63d360f886e8
parent 61b13365876dbcc641e246fe83b509b664da5d09
author Arya K Padman <aryakpadman@gmail.com> 1711702417 -0500
committer Arya K Padman <aryakpadman@gmail.com> 1711953116 -0500

PEL: Message_registry: System name as per new compatible interface

As part of the migration from IBMCompatible interface to the new
Compatible interface the PEL code is changed to use the new system name
format as 'com.ibm.Hardware.Chassis.Model.<system_name>'.

The message registry file still uses the old system name format
'ibm,<system_name>' which results parsing error of PEL message registry
callout JSON.

Hence modifies the message registry file to use the new system name
format.

Tested:
The dev_callouts file in /usr/share/phosphor-logging/pels/ have the new
system name format.
```
com.ibm.Hardware.Chassis.Model.Rainier1S4U_dev_callouts.json
com.ibm.Hardware.Chassis.Model.Rainier2U_dev_callouts.json
com.ibm.Hardware.Chassis.Model.Rainier4U_dev_callouts.json
```

Creating a PEL for SbeTimeout which leads to the PEL callouts as
expected:
```
"Callout Section": {
        "Callout Count":        "2",
        "Callouts": [{
            "FRU Type":         "Normal Hardware FRU",
            "Priority":         "Lowest priority replacement",
            "Location Code":    "U78DA.ND0.WZS004A-P0",
            "Part Number":      "02WG676",
            "CCIN":             "2E2D",
            "Serial Number":    "Y131UF07302J"
        }, {
            "FRU Type":         "Normal Hardware FRU",
            "Priority":         "Lowest priority replacement",
            "Location Code":    "U78DA.ND0.WZS004A-P0-C22",
            "Part Number":      "02WF429",
            "CCIN":             "6B59",
            "Serial Number":    "YL101314Y002"
        }]
    }
```

Signed-off-by: Arya K Padman <aryakpadman@gmail.com>
Change-Id: I438bb3de5014edd6a510e5334c8b1981d5ac512c