feat: implement contextualized ObjectStore

[waynr]

• chore(temporary): patch objectstore with local path
• feat: implement ContextualizedObjectStore that passes along session state via GetOptions
• chore: update temporary object_store patch rev

Which issue does this PR close?

• Closes Pass SessionConfig extensions to ObjectStore used during physical plan execution #14804.

Rationale for this change

See #14804

What changes are included in this PR?

Introduce new ContextualizedObjectStore type that implements object_store::ObjectStore.

Are these changes tested?

I haven't written any tests for this behavior in datafusion yet and would like guidance from maintainers with respect to what kind of testing they think would be good here.

I also still need to manually test that this does the thing I want it to do with respect to tracing in a caching ObjectStore implementation in https://github.com/influxdata/influxdb

Are there any user-facing changes?

Only if the user registers a custom ObjectStore implementation with datafusion and wants to pass opaque data (like tracing spans) from various places in the call stack leading up to query execution -- after this they will have access to that data in their custom implementation of ObjectStore.get_opts when called during query execution.