Add bcrypt as a dependency

CI was failing because the generated user model was being placed in the test directory as expected. I think the problem was that the test command was testing that file before it could be deleted. Since the user model contains a call to `has_secure_password` which requires bcrypt, CI was raising an error.

I think the larger the install command is, the slower the test suite will run, which will result in intermittent failures. I was not running into this locally because my machine simply has more resources.

Author: stevepolitodesign

.github/workflows/ci.yml

@@ -22,4 +22,4 @@ jobs:
       - name: Run Standard
         run: bundle exec standardrb
       - name: Run tests
-        run: bundle exec rails test test/rails_mvp_authentication_test.rb
+        run: bundle exec rails test

Gemfile

@@ -11,6 +11,7 @@ end
 
 group :development, :test do
   gem "standard", "~> 1.7"
+  gem "bcrypt", "~> 3.1.7"
 end
 
 # Start debugger with binding.b -- Read more: https://github.com/ruby/debug

Gemfile.lock

@@ -74,6 +74,7 @@ GEM
       minitest (>= 5.1)
       tzinfo (~> 2.0)
     ast (2.4.2)
+    bcrypt (3.1.16)
     builder (3.2.4)
     concurrent-ruby (1.1.9)
     crass (1.0.6)
@@ -189,6 +190,7 @@ PLATFORMS
   arm64-darwin-21
 
 DEPENDENCIES
+  bcrypt (~> 3.1.7)
   rails_mvp_authentication!
   sprockets-rails (~> 3.4, >= 3.4.2)
   sqlite3