Update rubocop version

[Splines]

Update rubocop version for use with the Ruby LSP VS Code extension (Language server that works hand in hand with a ruby formatter of your choice, in our case rubocop, and automatically detects rubocop settings).

[codecov]

Codecov Report

Merging #494 (4e09236) into mampf-next (b119ec9) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           mampf-next     #494   +/-   ##
===========================================
  Coverage       66.64%   66.64%           
===========================================
  Files             311      311           
  Lines            9362     9362           
===========================================
  Hits             6239     6239           
  Misses           3123     3123           

[fosterfarrell9]

I am confused that Gemfile.lock is unchanged. It still lists

rubocop (0.93.1)

and other old rubocop dependencies. Did you run

bundle update rubocop

inside the docker container? It should update the Gemfile.lock.
See also this article and the links there on why it is recommended to include Gemfile.lock in the repository (it is by default in a new Rails app; it seems that the consensus is to include it, and hence, have it up to date).

[Splines]

I am confused that Gemfile.lock is unchanged. It still lists

rubocop (0.93.1)

and other old rubocop dependencies.

Oh, good catch, I completely forgot about the lock file and instead updated the version number by hand. I ran

bundle update rubocop --conservative

now, (conservative to ensure to not update any other unrelated gems and keep this change focused) and this updated the lockfile accordingly.