Sidekiq not respecting geo_object_storage_verification feature flag

Summary

Sidekiq continues to run object storage verification despite geo_object_storage_verification feature flag being disabled

Steps to reproduce

1. Set up a GitLab instance with Geo enabled and object storage configured

2. Disable the geo_object_storage_verification feature flag:

   Feature.disable(:geo_object_storage_verification)

3. Monitor /var/log/gitlab/gitlab-rails/geo.log for verification errors

What is the current bug behavior?

Despite having geo_object_storage_verification disabled, Geo continues to attempt verification of CI job artifacts stored in object storage, resulting in: log noise "File is not checksummable" errors in geo.log

What is the expected correct behavior?

When geo_object_storage_verification is disabled, Geo should skip verification attempts for artifacts stored in object storage

Relevant logs and/or screenshots

{"severity":"ERROR","time":"2025-07-25T02:19:47.389Z","correlation_id":"a74004f2e726bf1b21bffda56aa8a3f0","class":"Ci::JobArtifact","gitlab_host":"xxxx.gitlab.in.xxx.com","message":"Error during verification","error":"File is not checksummable","id":198757646}

Output of checks

Feature.enabled?(:geo_object_storage_verification) 
=> false

Results of GitLab environment info

Expand for output related to GitLab environment info

GitLab v18.1.2