ID 426785 - The wrong codec is applied when reading in a grouped/gizmo Write node.

Problem summary
The wrong codec is applied when reading in a grouped/gizmo Write node.

Customer reported version
nuke.12.0v3

Customer reported platform
windows10

Steps to reproduce
1) From Nuke, create a Write node and set the file type to .mov.
2) Adjust the codec settings for Motion JPEG A.
3) Group the Write node (Ctrl+G), then select export as gizmo...
4) Save the gizmo to the .nuke directory and quit Nuke.
5) Launch Nuke and select the left toolbar for Other > All Plugins> Update.
6) Load the created gizmo for the Write node, expand the gizmo to view the contents, and observe the codec.

Expected behavior
The Motion JPEG A codec should be applied to the Write node from inside the Group/gizmo node.

Actual behavior
The Motion JPEG A codec is replaced with the Apple ProRes 4444 codec.

Workaround
Placing the following command in the menu.py allows for the gizmo's codec to be defaulted to Motion JPEG A:  nuke.knobDefault('name.gizmo', 'mjpa')

Reproduced by Support in
Nuke 12.1v1 - Windows 10, CentOS 7, macOS 10.14

Nuke 12.0v5 - Windows 10

Nuke 12.0v1 - Windows 10

Nuke 11.3v5 - Windows 10

Nuke 11.3v1 - Windows 10

Nuke 11.2v7 -  Windows 10

Nuke 11.2v1 - Windows 10

Nuke 11.1v1 - Windows 10

Nuke 11.0v1 - Windows 10

Nuke 10.5v1 - Windows 10

Nuke 10.0v1 - Windows 10

Nuke  9.0v1  - Windows 10, CentOS 7, macOS 10.13 - regression

Unable to reproduce bug in:
Nuke 8.0v7 - Motion JPEG A was the default value for .movs.

Earliest version tested
Nuke 8.0v7 - This issue doesn't appear in this version and has regressed