Add models for Primo Search API integration

[jazairi]

Why these changes are being introduced:

The first iteration of USE UI will include the
ability to toggle between Ex Libris CDI and
TIMDEX results.

Relevant ticket(s):

• USE-30

How this addresses that need:

This adds a Primo Search model that calls the
Primo Search API, and a Normalize Primo model that parses the each result and returns a normalized
record.

Side effects of this change:

• For better or worse, much of the normalization code has been repurposed from Bento. This felt
  acceptable as we do not anticipate this to be a
  long-term solution.
• While working on this, I noticed that most of the TIMDEX normalization logic happens in the
  views. It would be better to move this to
  a normalization model, as we've done here with
  Primo. I opened USE-73 to address this.
• It's not technically a side effect of this changeset, but it's worth noting that we still
  periodically see some GeoData test failures on
  random test runs. I've documented this in USE-72.

Developer

Accessibility

• ANDI or WAVE has been run in accordance to our guide.
• This PR contains no changes to the view layer.
• New issues flagged by ANDI or WAVE have been resolved.
• New issues flagged by ANDI or WAVE have been ticketed (link in the Pull Request details above).
• No new accessibility issues have been flagged.

New ENV

• All new ENV is documented in README.
• All new ENV has been added to Heroku Pipeline, Staging and Prod.
• ENV has not changed.

Approval beyond code review

• UXWS/stakeholder approval has been confirmed.
• UXWS/stakeholder review will be completed retroactively.
• UXWS/stakeholder review is not needed.

Additional context needed to review

Unfortunately, since this doesn't touch views or controllers, the best way to confirm functionality is through manually testing in the Rails console. You can try running a new search (search = PrimoSearch.new.search('popcorn', 10)), then grabbing a record from it (search['docs'].first), and looking at the normalized record (NormalizePrimo.new(record).normalize).

Code Reviewer

Code

• I have confirmed that the code works as intended.
• Any CodeClimate issues have been fixed or confirmed as
  added technical debt.

Documentation

• The commit message is clear and follows our guidelines
  (not just this pull request message).
• The documentation has been updated or is unnecessary.
• New dependencies are appropriate or there were no changes.

Testing

• There are appropriate tests covering any new functionality.
• No additional test coverage is required.

[coveralls]

Pull Request Test Coverage Report for Build 18170449977

Details

• 185 of 185 (100.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.3%) to 98.976%

---

Totals
Change from base Build 17475582805:	0.3%
Covered Lines:	773
Relevant Lines:	781

---

💛 - Coveralls

[JPrevost]

Initial feedback. Will formalize the review when you make the changes to normalizer you noted in Slack yesterday.

[jazairi]

@JPrevost I ended up pushing the changes in a few separate commits. The first fixes the bulk of the initial feedback. The second involved renaming the NormalizePrimo model, so it felt useful to make it a separate commit for ease of review. The last two commits are just things I forgot to address in the first commit. 🙂

Let me know if I missed anything, or if anything else comes up in the remainder of the review. Thanks!