Updated stripe_event to 2.3.0 and stripe to 5.14.0

[jdjkelly]

• stripe_event added support for stripe 5.x.x in 2.3.0: https://github.com/integrallis/stripe_event/blob/master/CHANGELOG.md#230-august-23-2019 - this is the only tagged version after the one currently in gemspec, so this alone seems safe
• By my reading of the git history, the only reason stripe was held below 5.x.x was because of stripe_events
• Updates stripe to latest at 5.14.0, which lists these breaking changes, with my notes in parenthesis:
  • Convert library to use built-in Net::HTTP stripe/stripe-ruby#813 (rewrites internals to use Net::HTTP, seems safe)
  • Make CardError's code parameter named instead of positional stripe/stripe-ruby#816 (no use of CardError in pay's codebase - seems safe)
  • Drop support for old versions of Ruby stripe/stripe-ruby#817 (drops Ruby 2.1 and 2.2 support, safe)
  • Remove old deprecated methods stripe/stripe-ruby#820 (method deprecation, potential risk)
  • Remove all alias for list methods stripe/stripe-ruby#823 (alias deprecation, potential risk)
  • Remove UsageRecord.create method stripe/stripe-ruby#826 (drops UsageRecord.create, seems safe)
  • Remove IssuerFraudRecord stripe/stripe-ruby#827 (removes IssuerFraudRecord, seems safe)
  • Remove a few more very old deprecated methods stripe/stripe-ruby#831 (method deprecation, potential risk)
• Test pass, though I'm not familiar enough with this codebase to know if that's a fake out

Otherwise, while I'm here:

1. Would you accept some other PRs related to tidiness? Ex. a PR to add frozen_string_literal to file headers - infamously has benefits in Ruby, and is currently throwing in your Rubocop config
2. Would you accept a number of other minor dependency updates? I can configure dependabot on my fork to make this manageable

[jdjkelly]

BTW, I'm going to start using my fork here in a quick MVP build out, I'll report back if I hit anything broken

[excid3]

Hey @jdjkelly

Just a heads up, the sca branch is probably going to become version 2.0 pretty soon. It's already supporting stripe_event 2.3 as well.

It's rebuilt everything for Stripe to support SCA payments and changed basically everything under the hood. Since it's the most forward compatible, I think it's the right place if you're starting with Pay right now.

[jdjkelly]

@excid3 awesome, thanks for letting me know - looking forward to more contributions