Feature: Better error or response handling when repo does not exist for voting

[bdougie]

Type of feature

🍕 Feature

Current behavior

Today a repo is submitted and does not exist in the API it presents an error (either 500 or 400 status code - @janie-lee-developer will need to share more context) message. The expectation is that the repo is added to a queue for indexing or instantly indexed.

Suggested solution

Provide a consistent response (200) code and message when a submitted repo and waiting to be indexed.

If the data is unavailable, it should show "sync in progress" or "updating" or similar.

Additional context

open-sauced/hot#394

Code of Conduct

• I agree to follow this project's Code of Conduct

Contributing Docs

• I agree to follow this project's Contribution Docs