Remove DB checks from Geo secondary check in user routes
What does this MR do and why?
We need to know whether the current site is a secondary or not to set the default Devise routes (that the app uses to redirect, create paths to etc).
Previously, this used the general check of GeoNode.exists? and verified that the current_node in the database has the secondary flag.
However, this ran queries in initializers, and we disallow that as it won't work for upgrading to Rails 7 either.
This now uses the geo_database_configured? check, on non-Geo nodes
or Geo primaries, this should not exist, as there is no tracking DB
and Omnibus / CNG don't add this config, while they add it for
Geo secondaries.
Related to #359913 (closed)
Screenshots or screen recordings
How to set up and validate locally
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.