Update gem dependencies that have security risks

[cy-by]

Comes from #296.

What does this PR do?

• Update gem dependencies that have security risks
  • Update rails to 5.2.4.6
  • Update bundler to 2.2.19
  • Update nokogiri
  • Update addressable
• Add run step in CircleCI to use v2 of bundler

Testing

Locally, I'm able to bundle install and run the application bin/rails s without issue.

I might be a good idea for whoever tests this PR, to pull it down locally and make sure a bundle install works properly.

[cy-by]

I had to add this run step in each job, install_dependencies, run_checks, and run_tests. If not, bundler v1 would be used and the job would fail.

I'm not really familiar with CircleCI config code, is there a way to define this once for all three jobs to use? So that this code can be DRY?

[bengolder]

@coltborg I believe that yes, you can define it once and reuse it for all three jobs. I think the GYR circle CI config has examples of defining a command and reusing it.

[bengolder]

This looks good to me! Thank you! I'm happy to pair on a followup commit to refactor/DRY the CircleCI config file.