Browser Persistence: Standardize Controller, Buttons, and Routes

[strouptl]

Changes

• Move browser persistence actions to dedicated controller
• Standardize browser persistence routes (post/delete rather than get/post)
• Use button_to (rather than link_to) for controls to reduce JS dependency
• Add tests for removing and clearing browser persistence

[strouptl]

@strzibny, these changes may require users to regenerate their devise_otp controllers/views if they have customized them in their application. I think the changes are needed, but we will need to announce them in the Changelog with the release.

Please let me know if you have any thoughts or comments.

Thanks!

[strouptl]

I don't like the "all_persistence" path name either. Maybe I will change this to "clear_all_browsers" for clarity (still with the DELETE HTTP verb).

[strouptl]

NOTE: I ended up renaming the "all_persistence" to "reset", and moving the actions to a dedicated controller.