Expand primo search beyond collection

[JPrevost]

Example search: A review on mixed mode fracture of metals in this branch versus in main will show different results. The results introduced in this PR match the expectations of stakeholders and can be confirmed using Primo UI.

Why are these changes being introduced:

• Results from Primo should include things we do not subscribe to so users can find and request them

Relevant ticket(s):

• https://mitlibraries.atlassian.net/browse/USE-233

How does this address that need:

• Adds the pcAvailability=true parameter to Primo search requests

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

E.g., if the PR includes updated dependencies and/or data
migration, or how to confirm the feature is working.

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 19835970485

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 97.833%

---

Totals
Change from base Build 19828164303:	0.0%
Covered Lines:	948
Relevant Lines:	969

---

💛 - Coveralls

[jazairi]

Sorry, forgot to finish this review yesterday! Confirmed different results display in this PR for the test query provided. I notice we're hardcoding the value of pcAvailability, but that feels okay to me because I doubt we'd ever want it to be false.