refactor: Move view and stream from datasource to catalog, deprecate View::try_new

[logan-keede]

Which issue does this PR close?

• part of [Epic] Split datasources out from datafusion crate (datafusion/core) #14444.

Rationale for this change

view and stream are TableProviders, catalog seems like the proper place for them considering their Table Providers and their dependency.

What changes are included in this PR?

just refactor of both.
I left test view at its original place for now.

Are these changes tested?

Testing by Github CI.

Are there any user-facing changes?

Nope, I have kept backward compatibility.

[m09526]

Looks all good!

[alamb]

Thanks @logan-keede -- this looks really nice

I have a few questions / comments about avoiding the datafusion-optimizer dependency -- let me know what you think

[alamb]

I think it would be really nice to avoid the new dependency on the datafusion-optimizer crate here --

However, it seems like it is related to the fact that coercion is part of the optimizer crate 🤔

I can think of two ways to avoid this:

1. Make the caller of ViewTable::try_new call coerce_types directly
2. Move the coercion into a new crate (seems overkill)

But the more I think about this the less of a problem I think it is

[logan-keede]

I have moved it to the only caller SessionContext, though I have a concern if there is a use case where someone might not want to use SessionContext but use ViewTable directly. since they will not get default Coercion now.

[alamb]

We can perhaps add a note to the upgrade guide

• https://github.com/apache/datafusion/blob/main/docs/source/library-user-guide/upgrading.md

The other thing we could do is add a new function and deprecate the old one, so the compiler would tell all users when they had upgrade 🤔 I will try and give this a shot

[alamb]

Thank you @logan-keede -- I pushed a commit to deprecate View::try_new and renamed the apply_required_rule

[xudong963]

Thank you