Determine whether Option::None fields should be serialized in Messages/Resources

[amika-sq]

In the tbDEX protocol spec, there are a lot of optional fields that can appear within a Resource/Message.

Currently, Rust will serialize those optional fields, even if they're empty. I don't believe that the spec explicitly defines if they should/shouldn't. We should come to resolution on this, and add in serialization skips for Option::None fields if they're necessary.

Link to comment with a few options on how we could handle this:
#37 (comment)

[mistermoe]

good callout @amika-sq !

I don't believe that the spec explicitly defines if they should/shouldn't.

will surface this discussion today so we can resolve