Replace Hints with Suggested Resources

[jazairi]

Why these changes are being introduced:

We've replaced the Hints system built into Bento with the Suggested Resources detector, provided by TACOS API. Since Bento is already logging search terms to TACOS in production, it makes sense to switch to using Suggested Resources.

Relevant ticket(s):

• TCO-66

How this addresses that need:

This removes the Hint feature and replaces it with Suggested Resources. We are currently triggering Suggested Resources in the same way as Hints (and the other controllers), but it might make sense to refactor this feature using a tool like Stimulus or Turbo. I've opened (ENGX-283)[https://mitlibraries.atlassian.net/browse/ENGX-283] to track further work on this.

While discussing this feature, we realized that GraphQL returns an array for suggestedResources even though that detector will only return a single resource. We are handling this in Bento by just calling first on the array, but we should reconsider whether the GraphQL type is returning the correct data structure. The spike ticket TCO-84 will further explore this problem space.

Side effects of this change:

• As far as I can tell, we don't really have a notion of hint source anymore, so I haven't tried to replicate the helper methods. This seems most pertinent to HintHelper#data_type, which professes to allow analytics tools to distinguish between hint sources. (It's unclear if this is still used by Matomo.) It also affects the display type, of which we have two for Hints, but that doesn't seem like a significant change.
• Debug and ClimateControl have been added to the Gemfile. The former is what we should be using to debug instead of Pry, and the latter was needed to test various ENV conditions.

Developer

• All new ENV is documented in README
• All new ENV has been added to Heroku Pipeline, Staging and Prod (Added to staging and prod)
• ANDI or Wave has been run in accordance to
  our guide and
  all issues introduced by these changes have been resolved or opened as new
  issues (link to those issues in the Pull Request details above)
• Stakeholder approval has been confirmed (or is not needed)

Code Reviewer

• The commit message is clear and follows our guidelines
  (not just this pull request message)
• There are appropriate tests covering any new functionality
• The documentation has been updated or is unnecessary
• The changes have been verified
• New dependencies are appropriate or there were no changes

Requires database migrations?

NO

Includes new or updated dependencies?

YES

[coveralls]

coverage: 99.123% (-0.09%) from 99.216%
when pulling 5464e64 on tco-66-hints-to-tacos
into 29fd71f on main.

[jazairi]

Merging without review since two engineers have worked on this, as discussed during our demo/retro this morning.