require to require_relative

[MSP-Greg]

Description

Change use of require to require_relative where appropriate.

Closes #2902

Actions macOS runners seem to be having some issues.

Your checklist for this pull request

• I have reviewed the guidelines for contributing to this repository.
• I have added (or updated) appropriate tests if this PR fixes a bug or adds a feature.
• My pull request is 100 lines added/removed or less so that it can be easily reviewed.
• If this PR doesn't need tests (docs change), I added [ci skip] to the title of the PR.
• If this closes any issues, I have added "Closes #issue" to the PR description or my commit messages.
• I have updated the documentation accordingly.
• All new and existing tests passed, including Rubocop.

[MSP-Greg]

Actions has issues earlier. I reran the test workflow's failed jobs. JFYI. passed

[nateberkopec]

This feels weird. Is this weird? I've never seen this before.

[MSP-Greg]

This feels weird. Is this weird? I've never seen this before.

If it's an absolute path, it 'bypasses' the RubyGems resolution. So

autoload :Const, "puma/const" resolved by RubyGems, similar to require
autoload :Const, "#{__dir__}/puma/const" resolved as a path, no RubyGems, similar to require_relative

The Ruby docs for Kernel.autoload show an absolute path, Module.autoload show a 'RubyGems' like path.

I think most code paths that are followed with 'normal' Puma use will see require_relative for all the files autoloaded here, so these are kind of helpers for running single test files. autload only does something if the constant isn't defined...