fix: #543 more properly identify CREATE TABLE ... LIKE ... statements

[markjm]

Resolves #543.

By skipping over setting LIKE statements as Comparisons during lexing phase. We then more thoroughly check its usage during grouping. If we are creating a TABLE (identified based on the rigid syntax documented here https://dev.mysql.com/doc/refman/8.0/en/create-table-like.html), then dont group as a Comparison, otherwise treat it as we did before.

• ran the tests (pytest)
• all style issues addressed (flake8)
• your changes are covered by tests
• [n/a] your changes are documented, if needed

[markjm]

cc @reata who opened the relevant issue and @andialbrecht as the maintainer of this awesome project :)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.06%. Comparing base (7334ac9) to head (8362373).
Report is 20 commits behind head on master.

❗ Current head 8362373 differs from pull request most recent head 1995a8c. Consider uploading reports for the commit 1995a8c to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #767      +/-   ##
==========================================
+ Coverage   97.04%   97.06%   +0.01%     
==========================================
  Files          20       20              
  Lines        1558     1566       +8     
==========================================
+ Hits         1512     1520       +8     
  Misses         46       46              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[markjm]

@andialbrecht resolved merge conflicts with recently merged #740

[markjm]

Hi @andialbrecht just wanted to check in on this change. Is this something you would be interested in incorporating? If so, i can keep the branch conflict-free