IdV Rate limiting events

[Sgtpluck]

🎫 Ticket

Link to the relevant ticket:
163

🛠 Summary of changes

Adding a general rate limiter event. Opening draft PR to run tests (feature specs seem to be broken locally)

[Sgtpluck]

these two additions and the document_capture_step_helper.rb addition seeme to make these tests run better (although not perfectly) locally -- am happy to remove though if it's adding to the noise of this larger PR

[Sgtpluck]

i wonder if there is a more holistically way to solve this issue :(

[mitchellhenke]

Yeah, I think based on similar discussion here and a follow-up in LG-16112 to find a more comprehensive fix, it's preferable to back out the page.has_content/button? changes.

Adding additional expectations for have_current_path seems good though.

[mitchellhenke]

One small removal suggestion

[mitchellhenke]

Suggested change

page.has_content? t('forms.buttons.back')

[Sgtpluck]

fixed in 02db17a

[mitchellhenke]

Should this be removed?

[Sgtpluck]

i added it because i was confused about why the tracker was receiving idv_rate_limited twice, based on the name of the test. i thought it might be helpful for other people like myself, but happy to remove it if you think it's not adding value. (very few folks have to dive into the tests of other teams in the way i'm doing it right now, after all)