Turbo: Consider replacing the default Turbo browser adapter with our own

Problem/Motivation

We're already heavily patching the Turbo browser adapter class for the progress bar, so we might as well tear the thing out and replace it with one that we provide, allowing us to hook into all the same visit callbacks as Turbo.

• Default Turbo browser adapter class
• Hotwire Native for Android adapter registration as an example
• Turbo handbook page about Hotwire Native

Steps to reproduce

👀

Proposed resolution

See above.

Remaining tasks

Assess what needs to be ported, what events we can move to the new browser adapter, etc.

User interface changes

None hopefully.

API changes

Maybe some additions in the form of new events? Unsure.

Data model changes

None.