Bump gitlab-pg_query gem to v1.3.1

This switches back to the upstream libpg_query, so we no longer need to
point to our own fork of the library. This also syncs the latest spec
changes with the upstream pg_query gem.

* https://gitlab.com/gitlab-org/pg_query/-/merge_requests/2
* https://gitlab.com/gitlab-org/pg_query/-/merge_requests/3

Gemfile

@@ -306,7 +306,7 @@ gem 'rack-attack', '~> 6.3.0'
 gem 'sentry-raven', '~> 3.0'
 
 # PostgreSQL query parsing
-gem 'gitlab-pg_query', '~> 1.3', require: 'pg_query'
+gem 'gitlab-pg_query', '~> 1.3.1', require: 'pg_query'
 
 gem 'premailer-rails', '~> 1.10.3'
 

Gemfile.lock

@@ -447,7 +447,7 @@ GEM
     gitlab-mail_room (0.0.8)
     gitlab-markup (1.7.1)
     gitlab-net-dns (0.9.1)
-    gitlab-pg_query (1.3.0)
+    gitlab-pg_query (1.3.1)
     gitlab-puma (4.3.5.gitlab.3)
       nio4r (~> 2.0)
     gitlab-puma_worker_killer (0.1.1.gitlab.1)
@@ -1361,7 +1361,7 @@ DEPENDENCIES
   gitlab-mail_room (~> 0.0.8)
   gitlab-markup (~> 1.7.1)
   gitlab-net-dns (~> 0.9.1)
-  gitlab-pg_query (~> 1.3)
+  gitlab-pg_query (~> 1.3.1)
   gitlab-puma (~> 4.3.3.gitlab.2)
   gitlab-puma_worker_killer (~> 0.1.1.gitlab.1)
   gitlab-sidekiq-fetcher (= 0.5.2)