KERI Version strings all legacy in example jsons

[daidoji]

This is a minor issue but one we should probably clear up before publishing.

All the examples use the legacy string format version and not the Version String to be published with the specification.

As per trustoverip/tswg-keri-specification#120 I think we should only publish examples using the updated version string format and leave the legacy version strings unmentioned as these are new specifications and although there are production deployments, these are small enough that new implementations based on these specifications shouldn't need to implement the legacy string version information.

(Note that this holds for both KERI and ACDC version strings)