AO3-7479 Remove unused gem awesome print

[sherin]

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-7479 (Please fill in issue number and remove this comment.)

Purpose

Removes unused gem awesome_print. The gem does not support rails 8.

(Hi! This is my first pull request. I picked an easy unresolved issue to get startted.)

Testing Instructions

How can the Archive's QA team verify that this is working as you intended?

As long as the automated tests pass, that should be enough I think. The gem was only added for test and dev environments.

Credit

What name and pronouns should we use to credit you in the Archive of Our Own's Release Notes?

Sherin (she)

If you have a Jira account, please include the same name in the "Full name"
field on your Jira profile, so we can assign you the issues you're working on.

Please note that if you do not fill in this section, we will use your GitHub account name and
they/them pronouns.

[Bilka2]

Hi, Sherin Kurian!

Thank you so much for this pull request. This PR looks good, so I've marked it as reviewed.

I've updated the Jira issue status to In Review so no one mistakenly creates a duplicate pull request. If you'd like the ability to comment on, assign, and transition issues in the future, you're welcome to create a Jira account! It makes things a bit easier for us on the organizational side if the Full Name on your Jira account either closely matches the name you'd like us to credit in the release notes or includes it in parentheses, e.g. "Nickname (CREDIT NAME)."

Once you've done that (or if you've already done it -- Jira has been unreliable about showing us new accounts in the admin panel lately), you can either reply here or send an email to otw-coders@transformativeworks.org with your account name and email address and we'll set up the permissions for you.

Thanks again for contributing! If you have any questions, you can contact us at the same email address listed above.

[sherin]

Thanks @Bilka2!

I sent an email to the address you linked with details to my jira account. I will wait until I have write access to the ticket before merging this PR.

Hi, Sherin Kurian!

Thank you so much for this pull request. This PR looks good, so I've marked it as reviewed.

I've updated the Jira issue status to In Review so no one mistakenly creates a duplicate pull request. If you'd like the ability to comment on, assign, and transition issues in the future, you're welcome to create a Jira account! It makes things a bit easier for us on the organizational side if the Full Name on your Jira account either closely matches the name you'd like us to credit in the release notes or includes it in parentheses, e.g. "Nickname (CREDIT NAME)."

Once you've done that (or if you've already done it -- Jira has been unreliable about showing us new accounts in the admin panel lately), you can either reply here or send an email to otw-coders@transformativeworks.org with your account name and email address and we'll set up the permissions for you.

Thanks again for contributing! If you have any questions, you can contact us at the same email address listed above.

[Bilka2]

I've given you permissions on Jira.

Just to be clear about the workflow here, PRs can only be merged by a few people. We generally collect a batch of PRs for a release and then merge, deploy and test them together as that batch.