AlecK/APPEALS-44512 - Zeitwerk Autoloader Transition

[AKeyframe]

Resolves APPEALS-44512 - Implement Zeitwerk Autoloading for eFolder

🛑🛑🛑 BEFORE DEPLOYMENT

• Requires AlecK/Zeitwerk to be merged into caseflow-commons.
• Requires caseflow Gem reference to be updated within the Gemfile.

🛑🛑🛑

Description

This PR makes the necessary changes to switch from classic autoloading to zeitwerk autoloading. This is in preparation for Rails 7.0, where classic autoloading will go from a deprecation warning to fully depreciated.

• See Rails Guides: Upgrading from Rails 6.1 to Rails 7.0

• See Rails Guides: Classic to Zeitwerk HOWTO

Acceptance Criteria

• Running bin/rails zeitwerk:check outputs "All is good!" message.

Testing Plan

• APPEALS-59305 Rails Zietwerk: eFolder local setup
• APPEALS-59307 [eFolder] - Rails Zietwerk PreProd(Build Only)
• APPEALS-59312 [eFolder] - Rails Zietwerk PRODTest(Pre-Regression)
• APPEALS-59322 [eFolder] - Rails Zietwerk UAT (Regression Testing)
• APPEALS-59329 [eFolder] - Rails Zietwerk prodTest (Regression Testing)

[amybids]

Is arranging these to be in alphabetical order necessary as a part of this work?

[jcroteau]

This was my doing, not Alec's. Is it necessary? No. But it was a good opportunity to leave something better than I found it, and it's a low-risk change. It was also done as a separate "refactor" commit before adding the new filter.

In general, I think it's a good practice to order things lexically to make them easier to parse (especially if it's a very long list). It also helps to avoid adding duplicate entries for things (which I almost did in this case, and that prompted me to do the reordering).