Consistent Spec Setup

[OutlawAndy]

Why?

There is a lot of boilerplate required to setup generator specs.

What Changed

What changed in this PR?

• remove much of the boilerplate required for most generator specs.
• Add replace_content Generator helper
• Improve JasminePlaywrightGenerator (issues explained below)
• capture stdout when running additional generators in flash & navbar specs. (specs that run other generators like this, still need to set their destination manually)

Pre-merge checklist

• Update relevant READMEs
• Update version number in lib/rolemodel_rails/version.rb

JasminePlaywrightGenerator issues:

• Rails.root does not work in this context (use source_root or destination_root)
• should raise an error if the generator cannot complete successfully
• .node-version already exists in the example apps. That was causing specs to lock up waiting for user to handle the file conflict. In this case, it's safe to force a replacement.
• Yarn cannot find the package @rolemodel/jasmine-playwright-runner without a valid github package token.

[wesrich]

I think this PR is fine, other than the internal node package being dropped. Once that comment is solved, it otherwise seems like it should be fine :)

[wesrich]

https://github.com/RoleModel/jasmine-playwright-runner/pkgs/npm/jasmine-playwright-runner

It's an internal package that requires some config. Presumably anyone that's running this generator should have that key.

Maybe instead of removing this dependency, we could check for the presence of this key/ENV variable, and add it to the array if it's available? (Or maybe this generator raises if the key doesn't exist, since I think the whole point is to install that one dependency?)

[OutlawAndy]

@wesrich. Would you mind pairing with me on implementing the check you're describing? I don't know what configuration I was expected to have in place and yarn only reported the package not being found.

I feel like the tests should confirm that it works, given the proper credentials.. But maybe it's not worth the GHA configuration that would require.. Opinion?

[OutlawAndy]

@wesrich I couldn't find any solid documentation on what is required to access our private packages. I found a reference to ENV['GITHUB_PACKAGE_TOKEN'] in the L.CAD Academy repo, so that's my best guess and I've updated the generator accordingly.. 🤷‍♂️