chore(data-warehouse): joins on views

[EDsCODE]

Problem

• joins on views don't work because the view names get parsed into the queries without a trace

Changes

• propogate a "view_name" on select queries so that they can be used to account for lazy joins
• in selectview, if a view_name is present, use the view_name to resolve the field types being requested. It might include lazyjoins that aren't present on the selectquery itself but will be once lazy tables are joined
• context: https://posthog.slack.com/archives/C019RAX2XBN/p1710868176668289

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Does this work well for both Cloud and self-hosted?

How did you test this code?

[EDsCODE]

TODO: this resolution logic is repeated from BaseTableType

[mariusandra]

This looks like it would work, but I wonder if this is inflating the responsibilities of SelectQueryAliasType just a bit? Seeing a view_type in that class doesn't tell me much about why it's there (and why it's not on e.g. SelectQueryType?).

This should either get a comment explaining its purpose... or alternatively I think a better approach is to create SelectViewType, either deriving from BaseTableType directly, or then as another entry in TableOrSelectType.

Note: this TableType could probably be renamed SelectTableType. TableAliasType to SelectTableAliasType, etc.