AO3-7457 Extract work blurb presenter

[nateberkopec]

Pull Request Checklist

• Have you read "How to write the perfect pull request"?
• Have you read the contributing guidelines?
• Have you added tests for any changed functionality?
• Have you added the Jira issue number
  as the first thing in your pull request title (e.g. AO3-1234 Fix thing)
• Do you have fewer than 5 pull requests already open? If not, please wait
  until they are reviewed and merged before creating new pull requests.

Issue

https://otwarchive.atlassian.net/browse/AO3-7457

Purpose

My end goal is to cache work blurbs, and to fetch them all in a single MGET for all relevant work blurbs.

In order to do this, we need a single place where we can make all the following decisions:

1. For each work, will we display the mystery or the full module?
2. Are we going to include the blurb "chrome" or not?
3. How many works are there?

The end goal is something that will look like:

render: WorkBlurbPresenter.new(@works), cached: true

... and that will Just Work, resulting in a single MGET cache call.

We can't do this without this presenter, primarily because of the mystery/non-mystery module distinction, which needs to be calculated on a per-work basis.

I also think this cleans up the code quite nicely:

1. The special case re: an admin viewing a users Works in Collections page is now taken care of on that page rather than in the partial.
2. A number of places where we weren't using collection: options got cleaned up
3. The logic on when a mystery blurb is appropriate is extracted to the presenter and much easier to read
4. A lot of that logic can now be tested in spec/presenters/work_blurb_presenter_spec.rb.

References

• Full Speedshop perf audit

[nateberkopec]

Note: this is_unrevealed thing was a no-op.

[nateberkopec]

Noticed a missing i18n, fixed.