chore: SNOS dependency customizations create duplicates in crate tree

[notlesh]

SNOS has been maintaining several forks of its dependencies for some time now. Many of our changes have been included in upstream, but there remain some minor ones which force us to continue to use our own forks.

This becomes very problematic for projects which use SNOS as a dependency (e.g. the prove_block lib) because it creates duplicated and conflicting dependencies which are difficult to work around, resulting in compile errors like:

note: `blockifier::Foo` and `Foo` have similar names, but are actually distinct types

Upstream PRs

As of now, each of these "customizations" has an upstream PR, listed below. However, these still point to main branches and would need to be backported for immediate relief (TODO).

• cairo-vm: Always use a normal segment for first SegmentArena segment lambdaclass/cairo-vm#1845
• sequencer: dev: Minor SNOS changes starkware-libs/sequencer#3098
• pathfinder: feat: Expose private class hashing functionality eqlabs/pathfinder#2465