feat: allow fetching certain entities at a specific revision id

[m90]

This allows users to pass an optional revid for each entity, locking the imported data to a fixed point in time.

In our setup this is required to fetch data from wikidata like it was before the introduction of the mul langiuage code.

[m90]

This change is unrelated to the feature, but was required to get the image building again.

[tarrow]

looks good and functional but I had to remind myself exactly how this case and pattern matching stuff works in bash

[m90]

Another option would be comparing the output of cut -d "@" -f 1 and cut -d "@" -f 2. If they are the same, there is no @ present. Would you find this easier to digest as a reader?

[tarrow]

Looks good to me; let's see this work.

My general "worries" is that we now have semi-nontrivial stuff in this image in bash, python and javascript but let's not worry too hard about this now.

[m90]

My general "worries" is that we now have semi-nontrivial stuff in this image in bash, python and javascript but let's not worry too hard about this now.

I've been thinking the same. In an ideal world, we'd use wb-cli as a library and have all logic live in a big node script. Maybe I can do that still when we know the feature is working.