ID 603349 - Camera4 and Axis4 nodes with expression driven values are not exported correctly by the GeoExport node

Problem summary:
Camera4 and Axis4 nodes with expression driven values are not exported correctly by the GeoExport node
 
This does not appear to impact other New 3D System nodes, such as SpotLight, DirectLight, and GeoCube.
 
Customer reported version:
Nuke Indie N/A
 
Customer reported platform:
Windows 11
 
Steps to reproduce:
1) Launch Nuke and create a Camera4 node in the Node Graph
2) Set the following expression on the Camera's translate x knob: (frame-1)/10
3) Create a GeoExport node, and export the Camera to a USD, USDA, or USDC file
4) Create a new Camera node, and enable the Import Scene Prim option
5) Set the File Path to the file exported in step 3
6) Then, set the Import Prim Path to /Camera1
7) Scrub through the timeline and observe how the imported camera has no animation.
 
Expected behavior:
The GeoExport node should write expression animations to the resulting file, like it does with keyframe animations.
 
Actual behavior:
When the New 3D System's Camera or Axis nodes have expression animations, the GeoExport node will not include these in the output USD file.
 
Workaround:
Bake the expression to keyframe animation by Right-clicking on an expression driven knob and selecting the Edit > Generate... option.
 
Reproduced by Support in:
Nuke 16.0v4 - Windows 11, macOS 14 Sonoma
Nuke 16.0v1 - Windows 11, macOS 14 Sonoma -- Regression 
 
Unable to reproduce bug in:
Nuke 15.2v4 - Windows 11, macOS 14 Sonoma
 
Earliest version tested:
Nuke 15.2v4 - This issue doesn't appear in this version and has regressed