Add Type Name to error message in CBOR conversion

[CodingVoid]

It was first a bit puzzling, when I got the error message. I think adding the problematic type greatly enhances finding the cause of ones problem.

[thomas-fossati]

It was first a bit puzzling, when I got the error message. I think adding the problematic type greatly enhances finding the cause of ones problem.

Great stuff. There's fallout on a couple of tests that need fixing:

• files_test.go:TestFiles_DoNotEncodeZeroLength

  Error Trace:    files_test.go:18
  Error:          Error message not equal:
              expected: "array MUST NOT be 0-length"
              actual  : "Files array MUST NOT be 0-length"

• processes_test.go:TestProcesses_MarshalCBOR/zero_elements

Error Trace:    processes_test.go:72
Error:          Not equal: 
                expected: &errors.errorString{s:"array MUST NOT be 0-length"}
            actual  : &errors.errorString{s:"Processes array MUST NOT be 0-length"}