Upgrade ViewComponent dependencies

[aduth]

🛠 Summary of changes

Upgrades ViewComponent and Lookbook to their latest respective versions, both of which are major upgrades:

• ViewComponent: 2.82.0 ➡️ 3.0.0
• Lookbook: 1.5.3 ➡️ 2.0.3

Notable breaking changes encountered:

• Trying to reference translation helpers in component constructor results in an error (see changes to PasswordToggleComponent)
• controller and request were removed from spec helpers, and were updated to equivalent vc_test_controller and vc_test_request.
• Slot API changes result in slot content rendering requiring a with_ prefix

📜 Testing Plan

• Spot check the application and component previews
• rspec

[aduth]

Based on spec failures, need to fix PasswordConfirmationComponent for similar reason as mentioned for translations in constructor as in PasswordToggleComponent. Will do that after merging #8466 to take advantage of specs being added for the component there.

[aduth]

Based on spec failures, need to fix PasswordConfirmationComponent for similar reason as mentioned for translations in constructor as in PasswordToggleComponent. Will do that after merging #8466 to take advantage of specs being added for the component there.

Fixed in rebased ce78d50.

I'm noticing a strange (seemingly harmless) Rack lint error when viewing component preview pages (example page):

Rack::Lint::LintError: Status must be >=100 seen as integer

It's followed by a 500 for a /components/cable/ request:

 "GET /components/cable/?uid=1684957888289 HTTP/1.1" 500 1637 0.2352

One of the changes in the Lookbook 2.0 upgrade related to actioncable dependency (docs). It was mentioned as optional, but given the 500, I'm curious how optional it really is. In any case, since Propshaft (#8457) requires one of the two mentioned dependencies (listen 🧚 ), I might try to see if the errors still happen after merging that pull request, and whether it's necessary to pull in actioncable as well.

[aduth]

I might try to see if the errors still happen after merging that pull request, and whether it's necessary to pull in actioncable as well.

I tried again after merging #8457 and it still happens. Troubleshooting more, it seems to be related to ActionCable responding with a -1 status code as part of its handling for Websockets, which Rack::Lint doesn't take kindly to. Generally, I think this is harmless aside from the terminal output, and affects only local development, and only on the /components/ routes, so I don't really feel too compelled to try to find a workaround.

See: rails/rails#26179