PG17 compatibility: Fix check-style, broken by PG17 columnar test fix… (#7776)

… (698699d89e)

---------

Co-authored-by: naisila <nicypp@gmail.com>

src/test/regress/sql/columnar_paths.sql

@@ -3,7 +3,7 @@ SET search_path TO columnar_paths;
 
 -- columnar_paths has an alternative test output file because PG17 improved
 -- the optimizer's ability to use statistics to estimate the size of a CTE
--- scan. 
+-- scan.
 -- The relevant PG commit is:
 -- https://github.com/postgres/postgres/commit/f7816aec23eed1dc1da5f9a53cb6507d30b7f0a2
 

src/test/regress/sql/multi_test_helpers.sql

@@ -612,9 +612,9 @@ BEGIN
   END LOOP;
 END; $$ language plpgsql;
 
--- This function formats EXPLAIN output to conform to how pg <= 16 EXPLAIN 
+-- This function formats EXPLAIN output to conform to how pg <= 16 EXPLAIN
 -- shows ANY <subquery> in an expression the pg version >= 17. When 17 is
--- the minimum supported pgversion this function can be retired. The commit  
+-- the minimum supported pgversion this function can be retired. The commit
 -- that changed how ANY <subquery> exrpressions appear in EXPLAIN is:
 -- https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=fd0398fcb
 CREATE OR REPLACE FUNCTION explain_with_pg16_subplan_format(explain_command text, out query_plan text)