Add Rails 7.1 support

[camertron]

What are you trying to accomplish?

This PR makes the changes necessary to support Rails 7.1.

Integration

No changes necessary in production.

List the issues that this change affects.

Fixes #2318

Risk Assessment

• Low risk the change is small, highly observable, and easily rolled back.
• Medium risk changes that are isolated, reduced in scope or could impact few users. The change will not impact library availability.
• High risk changes are those that could impact customers and SLOs, low or no test coverage, low observability, or slow to rollback.

What approach did you choose and why?

The only thing necessary to support Rails 7.1 is to remove an unnecessary require statement in the Rails engine. Rails 7.1 no longer adds eager load paths to Ruby's load path, preferring instead to let Zeitwerk autoload missing constants.

Accessibility

• No new axe scan violation - This change does not introduce any new axe scan violations.

[changeset-bot]

🦋 Changeset detected

Latest commit: 6892d11

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@primer/view-components	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[safeforge]

@camertron Removing the require "primer/form_helper" does not appear to be sufficient, but you have correctly identified the issue.

I'm experiencing issues with Form usage, and the error appears to be similar to the previous one: "cannot load such file -- primer/class_name_helper."

Indeed, by removing require "primer/class_name_helper" from the file lib/primer/forms/base_component.rb, the issue with my application appears to be resolved. I wonder if there are any other require causing errors.

[camertron]

@safeforge interesting, thanks for the heads-up. Let me see if I can get our test suite to fail, that would really help catch these issues.

[camertron]

Ok, I totally forgot to bump the framework defaults in the demo app's application.rb. Doing so uncovered several additional bad require statements that I have since removed.

@safeforge can you verify this addresses the issues you're seeing?

[jonrohan]

👍🏻

[safeforge]

@safeforge can you verify this addresses the issues you're seeing?

@camertron, I can confirm that your fix has resolved the issue in my use case. Thank you!