Fixes bug that causes out-of-order sstable key.

The previous way to address the problem was to replace \u{0000}
with 0 in different places.

This logic had several flaws:
Done on the serializer side (like it was for the columnar), there was
a collision problem.

If a document in the segment contained a json field with a \0 and
antoher doc contained the same json field but `0` then we were sending
the same field path twice to the serializer.

Another option would have been to normalizes all values on the writer
side.

This PR simplifies the logic and simply ignore json path containing a
\0, both in the columnar and the inverted index.

Closes #2442

bumping columnar version

low hanging fruit in optimization

oneshot 0.1.7

Now that the is_closed changed has been merge upstream, we can rely on
that.

This commit is a "hotfix" because we don't want to rely on
some of the commit in main just yet

update CHANGELOG, use github API in cliff (#2354)

* update CHANGELOG, use github API in cliff

* reset version to 0.21.1, before release

* chore: Release

* remove unreleased from CHANGELOG

chore: Release tantivy-tokenizer-api version 0.3.0

chore: Release tantivy-stacker version 0.3.0

chore: Release tantivy-sstable version 0.3.0

chore: Release tantivy-query-grammar version 0.22.0

chore: Release tantivy-common version 0.7.0