fix: [NO-TKT] update deprecated configs

When updating the rubocop gem in mob-api, rubocop was showing deprecation errors coming from this gem. This updates the rubocop configurations to fix those errors

Merge pull request #10 from silvercar/vvs-update-versions

Allow for newer versions of gems, instead of being completely locked …

Merge pull request #9 from silvercar/B2C-1371/ruby-update-for-b2c

[B2C-1371] Updated rubocop version '1.44.0' -> '1.48.0'

Merge pull request #8 from silvercar/NO-TKT/version-refresh

[NO-TKT] - Updating rubocop from   '1.18.4' to '1.44.0'

New config style and update Rubocop (#7)

Initial config was importing copy of config/default.yml instead of
using the one from the gem. Using that file from the gem should reduce
level of effort for future updates.

Adding rubocop-rake

Improving documentation around generation and use of todo file and
intent of `.rubocop.yml` vs `.rubocop_todo.yml` when used within a
project.

Update Rubocop (0.77 -> 0.78) (#6)

In 0.77, a type was introduced and in 0.78 that typo has been addressed

Update rubocop, performance, add thread_safety and rails (#5)

* Update Rubocop; Add modules Rails and Thread Safety

Use latest version of rubocop (0.77.0) and rubocop-performance (1.5.1),
add rubocop-thread_safety (0.3.4), add rubocop-rails (2.4.0).

Add known issue about Style/TrivialAccessors warning

Merge pull request #4 from silvercar/add-rubocop-yml

Add .rubocop.yml to gem

Merge pull request #3 from silvercar/publish-to-rubygems

Simplify CircleCI config to only build and publish gem