Prefer require_relative for internal requires

[tagliala]

Hi @deivid-rodriguez, I ran into an issue that you are probably familiar with while experimenting with GemBench

If you think this is a good change, I'll do the same for inherited_resources

---

require_relative is preferred over require for files within the same project because it uses paths relative to the current file, making code more portable and less dependent on the load path.

This change updates internal requires to use require_relative for consistency, performance, and improved portability.

Ref:

• Prefer require_relative for internal requires ruby/psych#522
• Prefer require_relative, it's a little bit faster. ruby/logger#20
• Prefer require_relative ruby/rdoc#658
• Benchmarks: are memowise results reliable? panorama-ed/memo_wise#349
• Prefer require_relative rubocop/rubocop#8748

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.31%. Comparing base (31c1487) to head (e122951).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #622   +/-   ##
=======================================
  Coverage   94.31%   94.31%           
=======================================
  Files          17       17           
  Lines         457      457           
=======================================
  Hits          431      431           
  Misses         26       26           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[deivid-rodriguez]

Yes, this is awesome and a nice practice ❤️. Thank you!