[substrait] Replace SessionContext with SessionState

[notfilippo]

Is your feature request related to a problem or challenge?

When producing / consuming a substrait plan it's not always practical to pass the SessionContext. Most of the methods used in the crate directly reference SessionContext even though all of them actually make use of the memory in its underlying SessionState.

Describe the solution you'd like

It should be possible to just use the SessionState when producing / consuming substrait plans.

Describe alternatives you've considered

As a next step we could possibly declare a trait with the subset of functions used by the substrait consumer / producer instead of requiring the SessionState object so users could provide their own context to the plan encoding / decoding functions.

Additional context

No response

[notfilippo]

take

[vbarua]

This is complementary to #13318