Introduce :gitlab_geo schema for Geo tracking DB

What does this MR do and why?

Add a :gitlab_geo schema in lib/gitlab/database/gitlab_schemas.yml similar to the separation between :gitlab_main and :gitlab_ci to ensure our query analyzers catch any cross-joins and cross-transactions.

Related to #358422 (closed)

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

app/workers/loose_foreign_keys/cleanup_worker.rb

@@ -34,7 +34,7 @@ def perform
     # If two DBs are configured (Main, CI): minute 1 -> Main, minute 2 -> CI
     def current_connection_name_and_base_model
       minutes_since_epoch = Time.current.to_i / 60
-      connections_with_name = Gitlab::Database.shared_database_base_models.to_a # this will never be empty
+      connections_with_name = Gitlab::Database.database_base_models_with_gitlab_shared.to_a # this will never be empty
       connections_with_name[minutes_since_epoch % connections_with_name.count]
     end
   end