Switch from ffjson to json-iterator

[nalind]

Per #886 (comment), replace our uses of ffjson with json-iterator.

[cevich]

Holy crap! Thanks @nalind !

Let me try rebasing my PR onto this to give it some runtime with the newer VM images...

[cevich]

With F34, I see one thing that appears like the tests simply need some adjusting.. I think that can be addressed in #886 so this LGTM (though I really don't fully understand the complete details).

[nalind]

Hmm, looks like Go 1.16's path/filepath.Match() is rejecting as syntactically invalid a test case that 1.15 accepted. Will take a closer look.

[rhatdan]

@nalind Will this cause an upgrade problem?

[rhatdan]

LGTM Depending on the question.
@vrothberg @saschagrunert @giuseppe PTAL

[giuseppe]

LGTM

[nalind]

@nalind Will this cause an upgrade problem?

I would be surprised. Which logic we call into to encode or decode structures should be an implementation detail that our consumers already don't have to care about outside of vendoring the deps, and the logic that reads and writes encoded data from and to files isn't changing.

[TomSweeneyRedHat]

Just to be sure, could we spin up a new c/storage and get it merged upstream into Buildah and Podman early next week?

[rhatdan]

Yup, just waiting for the dependabots to fire up.