Getting "Geo secondary database is not configured" when only running EE (sha_attribute)

What does this MR do?

Rescues the Geo::TrackingBase::SecondaryNotConfigured exception in sha_attribute, which allows a standard EE installation to start without the Geo secondary database configured.

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

A change to models/concerns/sha_attribute.rb causes an error during startup for EE (non-geo)

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• API support added
• Tests added for this feature/bug
• Review
  • Has been reviewed by UX
  • Has been reviewed by Frontend
  • Has been reviewed by Backend
  • Has been reviewed by Database
• EE specific content should be in the top level /ee folder
• Conform by the merge request performance guides
• Conform by the style guides
• Squashed related commits together
• Internationalization required/considered
• If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
• End-to-end tests pass (package-qa manual pipeline job)

What are the relevant issue numbers?

Closes #5926 (closed)