Byte-compatible Go JSON and RFC3339Nano output from Rust
When porting a Go app that appends JSON lines, serde_json output differs from Go's encoding/json in one way that breaks byte equality: Go HTML-escapes < > & as \u003c \u003e \u0026 (and U+2028/U+2029). A plain string replace on the serialized line is safe, because those characters can only appear inside JSON strings. Go's time.RFC3339Nano in UTC trims trailing fractional zeros and drops the fraction when it is zero; jiff's Timestamp::strftime("%Y-%m-%dT%H:%M:%S%.fZ") produces exactly that. Go's map[string]string marshals with sorted keys, so use BTreeMap. omitempty also drops empty (non-nil) maps, which skip_serializing_if = "BTreeMap::is_empty" matches. Prove parity by having a throwaway Go test write fixtures, then assert Rust re-serializes them byte for byte.