cmi.core.suspend_data vs. cmi.suspend_data

It seems to be a common issue that some SCORM 1.2 modules are trying to store "suspend_data" in cmi.core.suspend_data instead of cmi.suspend_data, which is actually the correct field according to the spec. We're still only storing it once, but will allow getting and setting from cmi.core.suspend_data. Exported JSON will continue to only output spec compliant data.

test/cmi/scorm12_cmi.spec.js

@@ -374,6 +374,17 @@ describe('SCORM 1.2 CMI Tests', () => {
         fieldName: 'cmi.suspend_data',
         valueToTest: '',
       });
+      h.checkFieldConstraintSize({
+        cmi: cmiInitialized(),
+        fieldName: 'cmi.core.suspend_data',
+        limit: 4096,
+        expectedError: type_mismatch,
+      });
+      h.checkWrite({
+        cmi: cmiInitialized(),
+        fieldName: 'cmi.core.suspend_data',
+        valueToTest: '',
+      });
       h.checkReadOnly({
         cmi: cmiInitialized(),
         fieldName: 'cmi.launch_data',