Update simdjson to 4.2.3 and introduce Builder API to do json encoding

[jimmystewpot]

We have been using the simdjson C++ library for some time. As we use more Rust, we have been looking at what the best option is for high-performance parsing of json. This library is one of the options we have evaluated.

In that evaluation, we bumped simdjson to 4.2.3 to implement the Builder interface, which is now part of the upstream C++ library. This introduces the ability to output json strings, so we can decode and encode with the same library easily.

Changes

• Update simdjson to 4.2.3
• Fix lifetime errors
• Fixed various serde bugs
• Added builder API support
• Added tests for various common JSON attacks (depth, etc)
• Some minor performance tweaks in the DOM parser by using &str instead of &String, which reduces allocations slightly

$ cargo run --release
   Compiling json-benchmark v0.0.1 (json-benchmark)
    Finished `release` profile [optimized + debuginfo] target(s) in 10.04s
     Running `target/release/json-benchmark`
                                DOM                  STRUCT
======= serde_json ======= parse|stringify ===== parse|stringify ====
data/canada.json         660 MB/s  1000 MB/s  1070 MB/s   860 MB/s
data/citm_catalog.json   620 MB/s  1660 MB/s  1570 MB/s  2000 MB/s
data/twitter.json        770 MB/s  2130 MB/s  1470 MB/s  2110 MB/s
data/apache_builds.json   840 MB/s  1970 MB/s  1590 MB/s  2150 MB/s

======= simd-json ======== parse|stringify ===== parse|stringify ====
data/canada.json         530 MB/s   890 MB/s   790 MB/s
data/citm_catalog.json  1900 MB/s  1740 MB/s  3030 MB/s
data/twitter.json       1890 MB/s  2010 MB/s  2390 MB/s
data/apache_builds.json  1740 MB/s  2060 MB/s  2090 MB/s

===== simdjson-rust ====== parse|stringify ===== parse|stringify ====
data/canada.json        1740 MB/s   490 MB/s 21240 MB/s   540 MB/s
data/citm_catalog.json  7050 MB/s  1210 MB/s 21060 MB/s  1520 MB/s
data/twitter.json       7180 MB/s  2210 MB/s 18570 MB/s  2490 MB/s
data/apache_builds.json  7070 MB/s  2060 MB/s 21210 MB/s  2430 MB/s

I bumped the versions in the Cargo.toml files, however I am not sure what your version logic is, so I just took a guess.

[jimmystewpot]

With further testing, we can confirm that #29 exists, and this appears to have been resolved by setting the lifetimes.