Modernize Hutch for 2.0.0 Release

[eglitobias]

Modernize Hutch for 2.0.0 Release

This PR prepares Hutch for a 2.0.0 release by removing EOL dependencies and modernizing documentation. Messaging infrastructure is critical for our systems, so maintaining this gem properly is a priority.

Breaking Changes

• Removed sentry-raven integration — EOL since 2019 (migration guide). Migrate to sentry-ruby with Hutch::ErrorHandlers::Sentry
• Removed ddtrace support — deprecated in favor of the datadog gem (migration guide)
• Replaced multi_json with stdlib json — one less dependency, same behavior. The multi_json gem is no longer actively maintained

Documentation Updates

• Updated README badges, requirements (Ruby 3.0+, RabbitMQ 3.13+), and links
• Modernized all RabbitMQ documentation URLs to https://www.rabbitmq.com/docs/
• Fixed typos and outdated examples
• Documented missing configuration options (graceful_exit_timeout, group)

Housekeeping

• Cleaned up dead Travis CI / Coveralls code
• Updated AGENTS.md and CHANGELOG.md

---

Feedback welcome! I believe we shouldn't continue supporting gems that have been deprecated for years. It creates maintenance burden and security risks. Happy to discuss any concerns about the breaking changes.

[michaelklishin]

@eglitobias thank you! That's an attitude that I really admire 👏

I have added a 2.0 milestone and will try to ship 1.4.0 in the next couple of days to clear the way for the 2.0 work you have in mind.

Also, I would be happy to add you as a repository contributor. Let me know if you'd be up for that :)

[eglitobias]

Thanks a lot. I really appreciate that, and I’d be happy to be added as a contributor.

Shipping 1.4.0 first sounds like a great idea to clear the way for 2.0. I’m happy to help with the 2.0 release and related work. I’ll be offline for the next 4 days, but I can jump in after that.

Also, I really appreciate your work on this. I was impressed by how quickly you upgraded the bunny and amq-protocol dependencies to support better error handling. 👏

[eglitobias]

@michaelklishin Thanks a lot, and great to see that #418 has now been merged.

I've now also rebased this branch on top of the latest main.

Since the actual 1.4.0 release still still needs to be created, I'd be happy to take care of it if that's helpful and if you'd like to grant me the necessary rights. But if you'd prefer to handle the release yourself, that's completely fine too.

[michaelklishin]

@eglitobias thank you.

Messaging infrastructure is critical for our systems, so maintaining this gem properly is > a priority.

Exactly the folks with this kind of attitude should have a say in how open source
software is maintained. I have invited you to be a collaborator in this repo.

[eglitobias]

@michaelklishin Thank you so much. I really appreciate the trust.