Validate binary column exists, in dev when geo is enabled

What does this MR do?

Related issue: #232766 (closed)

This MR changes the conditions for running a validation check on binary column existence.

It will now run only in development and when geo is enabled.

Without this change, a warning is issued in non-production environments even if geo is not enabled. This is pointless for developers who are not developing for Geo.

(Skipping a changelog entry since this is only relevant for non-production environments.)

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team