[EPIC] Easier extension configuration SessionState / SessionConfig

[alamb]

Is your feature request related to a problem or challenge?

Part of the discussion of keeping the core more modular is to move move functionality into "extension packages" to leverage DataFusion's extensibility APIs

Part of making extension packages compelling is ensuring it is easy / convenient to configure DataFusion to use these extensions. This will reduce the pressure for us to add more features to the core datafusion repo

As @matthewmturner and myself have been working on integrating some extension packages as part https://github.com/datafusion-contrib/datafusion-dft I have come across some things that would make it easier to configure DataFusion

Describe the solution you'd like

In general, I believe the SessionStateBuilder added by @Omega359 in #11403 is the obvious API to consolidate configuration

This ticket tracks various tickets for making it easier to use SessionStateBuilder to configure extensions

Describe alternatives you've considered

• Add enable_url_table as a argument to SessionStateBuilder #12394
• Make SessionContext::enable_url_table consume self #12551
• Support adding a single new table factory to SessionStateBuilder #12552
• Support Register object stores via SessionStateBuilder #12553
• Make it clearer that RuntimeEnv::new() is fallable #12554
• Implement Debug for `SessionStateBuilder #12555

[Omega359]

@alamb - this looks to be completed?

[alamb]

Thanks for the ping @Omega359 -- I agree