ID 470909 - If a Bake Point node is automatically set to "ACES - ACEScg" colourspace, exporting with $COLORSPACE variable produces "mari_float" instead

Problem summary
If a Bake Point node is automatically set to "ACES - ACEScg" colourspace, exporting with $COLORSPACE variable produces "mari_float" instead

Customer reported version
Mari 4.7v2

Customer reported platform
Windows 10

Steps to reproduce

1) Open any project, and in the project settings (File > Settings) change the OCIO config to ACES

2) Create a Cloud node

3) Create a Bake Point node with the Depth set to 16bit (Half) and connect the Cloud node to its input

4) Click Bake in the Bake node's properties, then in the Export tab, click Export Baked

5) Enter a filename in the Template field which includes the variable "$COLORSPACE" and click Export All Patches

Expected behaviour
The texture should be exported, with the $COLORSPACE variable in the template replaced by "ACES - ACEScg" e.g. the template "MyTexture_$COLORSPACE.exr" would create the filename "MyTexture_ACES - ACEScg.exr"

Actual behaviour
The $COLORSPACE variable is replaced by "mari_float" e.g. "MyTexture_mari_float.exr"

Workaround
The correct colourspace name is produced if the Bake Point colourspace is selected manually in the node properties

Reproduced by support
This bug has been reproduced in:
Mari 4.7v2 - Windows 10 - CentOS 7.7
Mari 4.7v1 - Windows 10
Mari 4.6v1 - Windows 10
Mari 4.5v1 - Windows 10
Mari 4.2v1 - Windows 10
Mari 4.1v1 - Windows 10 - CentOS 7.7 - regression

Unable to reproduce bug in:
Mari 4.0v4 - Windows 10 - CentOS 7.7

Earliest version tested
Mari 4.0v4 - This issue doesn't appear in this version and has regressed