Fix quoted reserved identifier 5.3

[spena]

Description

This is a backport from #3222

Testing done

Describe the testing strategy. Unit and integration tests are expected for any behavior changes.

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 #")

[spena]

@agavra I had to support SET and UNSET here because the KsqlEngineTest tests were failing (shouldSetPropertyInRunScript and shouldUnsetPropertyInRunScript).

But now the ensure-formatter.json is failing because SET is supported.

• Having SET supported in SqlFormatter is good?
• Should I remove the two test cases above (they're not in master)
• Or, should I add a different statement in the ensure-formatter that fails?

[agavra]

Hmmm... SET support is a good thing. I just couldn't think of another good way for ensure-formatter to work. I'm happy to get suggestions. (I don't think we should remove the existing tests because 5.3. depends on that). One option is to remove ensure-formatter for this PR

[spena]

I removed it so I can move forward.

[agavra]

LGTM - we're going to need to figure out how to merge this with master (we'll need to update ensure-formatter.sql if we're adding support for SET/UNSET in the formatter)

[spena]

Thanks @agavra, I found that SHOW TOPICS is also helpful to validate the ensure-formatter.json. I put the test back and it works. I will merge it with master.