Quash require_dependency warnings with newer Rails

[flavorjones]

Rails warnings look like:

DEPRECATION WARNING: require_dependency is deprecated without replacement and will be removed
in Rails 9.

- Recommendations for applications:

    - If the call is an old one written in the days of the classic autoloader to ensure a
      certain constant is loaded for constant lookup to work as expected, you can simply
      remove it.

    - In order to preload classes when the application boots, which may be necessary for
      things like STIs or Kafka consumers, please check the autoloading guide for modern
      approaches.

- Recommendations for engines that depend on Rails >= 7.0:

  Same recommendations as for applications, since the classic autoloader is no longer
  available starting with Rails 7.0.

- Recommendations for engines that support Rails < 7.0:

  Guard the call with a version check just in case the parent application is using
  the classic autoloader:

      require_dependency "some_file" if Rails::VERSION::MAJOR < 7

[Copilot]

Pull request overview

Updates Easymon’s controller loading logic to avoid require_dependency deprecation warnings on newer Rails versions, while preserving compatibility with older Rails classic-autoloader setups.

Changes:

• Guard require_dependency "easymon/application_controller" behind a Rails::VERSION::MAJOR < 7 check to prevent deprecation warnings on Rails 7+.

Tip

If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.