feat: add machine readable error output that can be serialized to any type

[zelosleone]

closes #7

will also close this one too hopefully: prefix-dev/rip#104

• added serialize and deserialize features (thanks wolf) without any hardcoding into json, so that users can just do what they want (thanks Bas)
• we already had human readable output that can be called via display_user_friendly function (damn i missed this, i feel too dumb)
• users can just use whatever they want either display_user_friendly or serializable machine outputs with all the machine readable outputs into any format they want

[baszalmstra]

@zelosleone I don't think the functionality of this PR is useful if it doesn't also include ecosystem-specific information. At the moment, the PR serializes IDs, which is completely useless because those IDs heavily depend on the implementation of the DependencyProvider and the Interner that created them at runtime.

It is also not enough to serialize the display strings because it would require parsing them back to ecosystem information, which is not trivial. Instead, the ecosystem provider should itself provide serialization for these fields, perhaps through another trait.

But even in the bigger picture, why is this useful? You link to a RIP issue, but don't you think it would be much more useful for that issue if the conflict were reduced to something that makes more sense for the consumption of downstream tools?