Crawlee v4 adds the Session-scoped fingerprint.

As discussed in this comment, different session consumers might interpret the same fingerprint with different implementation details. This might create a discrepancy between the implementations and possibly hurt the antiblocking performance of the crawler.

More investigation is needed here, though - is this an actual issue?