raise SecondaryNotConfigured if Geo DB is not found

What does this MR do?

For the Geo tracking database, captures the ActiveRecord::NoDatabaseError and raises a Geo::TrackingBase::SecondaryNotConfigured instead

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

Why was this MR needed?

When setting up a fresh Geo install using the GDK, make geo-setup was causing ShaAttribute to blow up when the tracking database was not found yet, which make geo-setup was in the middle of creating.

See gitlab-development-kit#373 (closed)

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
• Conforms to the code review guidelines
  • [-] Has been reviewed by a UX Designer
  • [-] Has been reviewed by a Frontend maintainer
  • Has been reviewed by a Backend maintainer
  • [-] Has been reviewed by a Database specialist
• EE specific content should be in the top level /ee folder
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• [-] Conforms to the database guides
• If you have multiple commits, please combine them into a few logically organized commits by squashing them
• [-] 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-and-qa manual pipeline job)

What are the relevant issue numbers?

gitlab-development-kit#373 (closed)