fix: Add requestJsonAndCheck204 to properly handle 204 status checks

[wavebyrd]

Summary

Methods that check for 204 status now properly raise exceptions for error codes (401, 403, 500, etc.) while still allowing 404 to return False.

Problem

As described in #2760, methods like is_merged() use requestJson and check status == 204. This causes:

1. False negatives - A PR could be merged but is_merged returns False if credentials are expired
2. Silent failures - Consumer is not notified that authentication has expired

Solution

Added a new requestJsonAndCheck204() method in Requester.py that:

• Returns True for status 204 (success)
• Returns False for status 404 (not found - valid response for "not merged")
• Raises appropriate exceptions for other error codes (401, 403, 500, etc.)

Changes

• Added requestJsonAndCheck204() method to Requester
• Updated example methods to use the new pattern:
  • PullRequest.is_merged()
  • NamedUser.has_in_following()
  • Repository.create_repository_dispatch()

Note

This PR establishes the pattern. There are ~40 other methods that use status == 204 that could be updated similarly. I can update them all if the maintainers approve this approach, or they can be updated incrementally.

Fixes #2760

🤖 Generated with Claude Code

[wavebyrd]

Ping - this fixes 204 status handling in API checks. Ready for review!