feat: Introduce materialization support for tables using CTAS to make tables queryable

[cprasad1]

Description

Introduces materialization support for tables using CTAS to make tables queryable.
We can make tables queryable by using:
CREATE TABLE QUERYABLE_TABLE AS SELECT...

This would help fix #4614 by adding a more helpful error message as well.

Testing done

• Unit tests
• Query translation tests

Reviewer checklist

• Ensure docs are updated if necessary. (eg. if a user visible feature is being added or changed).
• Ensure relevant issues are linked (description should include text like "Fixes #")

[ghost]

@confluentinc It looks like @cprasad1 just signed our Contributor License Agreement. 👍

Always at your service,

clabot

[vvcephei]

Thanks, @cprasad1 !

I can't speak to many of the little changes in internal method calls, etc., but at a high level, the error message and the tests look good: exactly what we wanted to achieve.

Minor note: we prefer "queryable" to "queriable".

Also, specifically in the tests, I'm wondering if we can re-structure them to be a little more compact and have better coverage, something like this:

• Have each case set up a CT or CTAS statement for query in a slightly different way, covering all the possible permutations (like a basic select *, one that includes a WHERE clause, one that includes a more complicated projection, one that does both, one that does a groupBy agg from a stream, one that does a join, etc. etc.).
• Then, inside each case, we just run multiple pull queries, for each slight variant of pull queries we want to test

In other words, we vary the queriable object between tests and vary the pill queries within each test. That way, we strike a good balance between code coverage and proliferation of test cases.

[AlanConfluent]

I just had a few small comments, but looks good.

[guozhangwang]

The PR LGTM, but I had a meta question regarding the description:

CREATE TABLE QUERYABLE_TABLE AS SELECT...

Are we really going to augment the syntax? In this PR it seems we just make CTAT always materialized anyways.

[cprasad1]

The PR LGTM, but I had a meta question regarding the description:

CREATE TABLE QUERYABLE_TABLE AS SELECT...

Are we really going to augment the syntax? In this PR it seems we just make CTAT always materialized anyways.

@guozhangwang what are you referring to when you say "augment"? If you were referring to the QUERYABLE_ part of QUERYABLE_TABLE, then that is just the dummy name of the table that is just used as an example here

[guozhangwang]

@guozhangwang what are you referring to when you say "augment"? If you were referring to the QUERYABLE_ part of QUERYABLE_TABLE, then that is just the dummy name of the table that is just used as an example here

My bad, I thought it was some new keywords :P

[vvcephei]

Thanks, @cprasad1 !