Query String line breaks not rendered correctly

[rmoff]

Describe the bug

The output for SHOW QUERIES does not render Query String correctly if there are line breaks present

To Reproduce

ksqlDB : 0.8.0

Create a query:

CREATE TABLE CUSTOMER_SUMMARY AS 
    SELECT C.FIRST_NAME + ' ' + C.LAST_NAME AS FULL_NAME, 
           C.EMAIL, 
           MAX(T.AMOUNT) AS LARGEST_ORDER
    FROM   TXNS T 
             LEFT JOIN 
           CUSTOMERS C 
             ON T.CUSTOMER_ID=C.ROWKEY 
    GROUP BY C.FIRST_NAME + ' ' + C.LAST_NAME, 
             C.EMAIL
    EMIT CHANGES;

View the query:

ksql> SHOW QUERIES;

 Query ID                | Status  | Sink Name        | Sink Kafka Topic | Query String
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 CTAS_CUSTOMER_SUMMARY_7 | RUNNING | CUSTOMER_SUMMARY | CUSTOMER_SUMMARY | CREATE TABLE CUSTOMER_SUMMARY WITH (KAFKA_TOPIC='CUSTOMER_SUMMARY', PARTITIONS=1, REPLICAS=1) AS SELECT  ((C.FIRST_NAME + ' ') + C.LAST_NAME) FULL_NAME,  C.EMAIL EMAIL,  MAX(T.AMOUNT) LARGEST_ORDERFROM TXNS TLEFT OUTER JOIN CUSTOMERS C ON ((T.CUSTOMER_ID = C.ROWKEY))GROUP BY ((C.FIRST_NAME + ' ') + C.LAST_NAME), C.EMAILEMIT CHANGES;
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
For detailed information on a Query run: EXPLAIN <Query ID>;

Expected behavior

Replace line breaks with spaces, don't delete them

ksql> SHOW QUERIES;

 Query ID                | Status  | Sink Name        | Sink Kafka Topic | Query String
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 CTAS_CUSTOMER_SUMMARY_7 | RUNNING | CUSTOMER_SUMMARY | CUSTOMER_SUMMARY | CREATE TABLE CUSTOMER_SUMMARY WITH (KAFKA_TOPIC='CUSTOMER_SUMMARY', PARTITIONS=1, REPLICAS=1) AS SELECT  ((C.FIRST_NAME + ' ') + C.LAST_NAME) FULL_NAME,  C.EMAIL EMAIL,  MAX(T.AMOUNT) LARGEST_ORDER FROM TXNS T LEFT OUTER JOIN CUSTOMERS C ON ((T.CUSTOMER_ID = C.ROWKEY)) GROUP BY ((C.FIRST_NAME + ' ') + C.LAST_NAME), C.EMAIL EMIT CHANGES;
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
For detailed information on a Query run: EXPLAIN <Query ID>;

Additional context
This may seem like a nit but being able to use the Query string as a way to rebuild one's application history after prototyping is useful, but scuppered if it's full of invalid code (e.g. MAX(T.AMOUNT) LARGEST_ORDERFROM TXNS)