Solver job_offers endpoint and matcher report different job offers

[bgins]

General Description

A query to the job_offers endpoint sometimes reports a different job offers than those logged by the matcher.

Which system(s) or functionality does this affect

This issue affects the solver. None of the other services query the job_offers endpoint, but humans query it to check if their job offer was posted.

Describe the changes, and how this affects/ interacts with each system.

Needs investigation. Initial thoughts are that there may be inconsistency between the store used by the Solver controller and the Solver server. Are we making a copy of the store that gets out of sync?

The issue may be resolved with #445 where we are adding a database backing for job offers.