Is your feature request related to a problem or challenge?

There are many functions in datafusion-core that take SessionState as arguments but only actually rely on portion of them. This add the additional dependency that is not necessary, therefore blocking us from extracting module out of core #10782.

For example, If we want to pull CatalogProvider out of core, we need to pull out TableProvider first. But because it has scan function that takes SessionState which contains CatalogProviderList therefore there is a circular dependency. Similar issues are already mentioned in #11182

Describe the solution you'd like

I think we need to redesign those functions that take SessionState and minimize the dependencies for them.

Given one of the scan function here, we can see that we only need state.config_options().explain and state.execution_props() instead of the whole SessionState

In this case, we can create TableProviderConext that encapsulates a subset of the information from SessionState.

pub struct TableProviderConext {
    explain_options: ExplainOptions,
    executionProps: ExecutionProps // maybe with reference to avoid copy
}

The same idea applies to PhysicalPlanner, we usually just need PhysicalOptimizeRules or other information about plan.

And, create_initial_plan in DefaultPhysicalPlanner, ExecutionOptions is all we need, nothing else.

Describe alternatives you've considered

No response

Additional context

No response