Rework to be a proper Rails plugin

[OutlawAndy]

Why?

1. This gem eager loads all generator classes during host application boot. This is unnecessary and actually goes against Rails best practices. I've recently learned that the proper way to supply generators to a Rails app requires a Railtie / Engine to notify the host application of their location on the file system and allow the host app to lazy load them if/when needed.
2. This gem introduces 2 top-level namespaces (Rolemodel & RolemodelRails) which is a general anti-pattern for RubyGems.
3. Naming convention for plugins like this one are to use a - rather than a _. e.g. rspec-rails, slim-rails, rubocop-rails, etc. This ties back into #2 because rolemodel-rails translates to Rolemodel::Rails, while rolemodel_rails translates to RolemodelRails.

What Changed

What changed in this PR?

• rename to rolemodel-rails
• add an Engine file to properly notify the host app about the generators
• don't eager load generators
• fix test setup which does need all constants that are tested to be eager loaded.
• Update the recreate_current_example script to use the AppGenerator with dummy_app set to true. (this is how the Rails PluginGenerator does it)
  • I left the legacy app generation script alone, because I couldn't get the AppGenerator to actually build a legacy Rails app. It will only build apps consistent with the current version, even if the gemfile points to an old version.
• use a modified boot.rb file in the example app which points to the plugin, rather then adding the plugin to it's gemfile (also how the Rails PluginGenerator does it)

Future Considerations

As a "Rails Plugin" with a Railtie/Engine file, there may be specific functionality which we decide to fold into RolemodelRails. Instead of everything being a generator and all code living in each project code base, we might opt to treat some features as provided by the engine and therefor upgradable via bundle update.

Pre-merge checklist

• Update relevant READMEs
• Run bin/bump_version or bin/bump_version --patch

[Copilot]

Pull request overview

Reworks the gem into a proper Rails plugin by renaming it to rolemodel-rails, introducing a Rails Engine for generator registration, and removing generator eager-loading during host app boot.

Changes:

• Renames the gem from rolemodel_rails to rolemodel-rails and collapses the public namespace to Rolemodel.
• Adds a Rolemodel::Engine to register generator support without eager-loading all generators at boot.
• Updates specs, example apps, and tooling scripts to use the new gem name and loading behavior.

Reviewed changes

Copilot reviewed 16 out of 24 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
spec/support/helpers/example_app.rb	Updates Gemfile cleanup to remove rolemodel-rails entries in the test app.
spec/spec_helper.rb	Updates spec bootstrapping to load Rails + the gem and eagerly require generator classes for tests.
spec/rolemodel_rails_spec.rb	Updates version constant expectations to the new Rolemodel namespace.
spec/generators/rolemodel/github_generator_spec.rb	Updates expected template text to reference the new version file path.
rolemodel-rails.gemspec	Renames the gem, updates metadata, and points version loading at Rolemodel::VERSION.
lib/rolemodel_rails.rb	Removes the old entrypoint that eagerly loaded generators.
lib/rolemodel/version.rb	Moves version constant under Rolemodel module.
lib/rolemodel/engine.rb	Adds Rails Engine for generator registration.
lib/rolemodel-rails.rb	Adds new gem entrypoint that defines version constants and requires version/engine.
lib/generators/rolemodel/base_generator.rb	Introduces a standalone BaseGenerator (previously defined in lib/generators/rolemodel.rb).
lib/generators/rolemodel.rb	Removes the old generator aggregator that loaded all generators eagerly.
example_rails8/Gemfile / Gemfile.lock	Updates example app to depend on rolemodel-rails.
example_rails7/Gemfile / Gemfile.lock	Updates example app to depend on rolemodel-rails.
bin/recreate_legacy_example	Updates bundle add invocation to rolemodel-rails.
bin/recreate_current_example	Updates bundle add invocation to rolemodel-rails.
bin/console	Updates require to rolemodel-rails.
bin/bump_version	Updates paths and gemspec name used by the version bumper.
README.md	Updates documentation to reference rolemodel-rails.
Gemfile / Gemfile.lock	Updates development dependency name to rolemodel-rails.
.gitignore	Adds .DS_Store ignore.
.github/workflows/ci.yml	Updates runner and GitHub Action versions used in CI.

Comments suppressed due to low confidence (1)

rolemodel-rails.gemspec:5

• rolemodel-rails.gemspec no longer has # frozen_string_literal: true at the top. This repo consistently uses frozen string literals in Ruby files, and removing it may introduce RuboCop/style inconsistencies.

Suggestion: add the frozen-string-literal magic comment back at the top of the gemspec (before any require).

[OutlawAndy]

@copilot open a new pull request to apply changes based on the comments in this thread

[Copilot]

@OutlawAndy I've opened a new pull request, #182, to work on those changes. Once the pull request is ready, I'll request review from you.

[timirwin]

Looks wonderful. Just a few questions to ponder. You may not need any changes if they all check out.

[timirwin]

@OutlawAndy Since this is public repo and running on Github, do we need to (or want to) switch to Blacksmith?

[OutlawAndy]

good question. I don't know. blacksmith is significantly faster, but might be safest to switch back. 👍

[timirwin]

Would we want to have rubocop verify the output of our generator's output?

[OutlawAndy]

I think one of our generators sets up running the rubocop formatter against generated files.. @wesrich can you confirm?

[timirwin]

Should we use the alias or keep it long form (binding.break)? Fine either way if binding.b is common knowledge.