consistent namespace convention

[dschwartznyc]

To support serialization testing, updated the Rune name space and JSON @type to facilitate consistent testing

• New feature (non-breaking change which adds functionality)

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: dschwartznyc (b82962f)
• ✅ login: davidalk / name: David Al-Kanani (67336bc, e387734)

[davidalk]

The round trip tests all take an input, deserialise it into a Rune object, then serialise it out and assert that the before input matches the resulting output. The error handling tests will assert an error when you attempt to serialise back out on that last step. Could we rename all these error namespaces to remove the roundtrip to avoid confusion. How about serialization.test.error...

[dschwartznyc]

Not plussed about the specific naming as long as there are no clashes and there's a clear delineation between the collection of tests that are expected to pass and the collection that are expected to fail. We use that distinction to automatically differentiate the tests according to their expected outcomes (assert pass vs assert fail).

For example:

passing tests: serialization.test.pass...
failing tests: serialization.test.fail...