Fix fakeredis count system

[alain-andre]

Fix error due to fakeredis and use a real one like other tests. It fixes also some errors like about status in returned json (not job[status]) and quotas mistake.

@fab-girard, @braktar we were not agree where to put the count_increase for an optimization, this still can be moved. Do we want to increase the count every time a VRP is valid or only when a full result is given ?

The only errors and failures are now due to known build_detail method, rubocop (@senhalil), a random time test and array that should be empty.

[senhalil]

@alain-andre I don't know why you tagged me for rubocop?

Rubocop rules are changed in PR #68 and it is merged recently without fixing the new errors due changed rules. I am not surprised that it fails.

[alain-andre]

@alain-andre I don't know why you tagged me for rubocop?

Rubocop rules are changed in PR #68 and it is merged recently without fixing the new errors due changed rules. I am not surprised that it fails.

Ok, I did not notice this, I still had in mind that fixing rubocop to v1.81 was enough not to break tests. I'll check.

[senhalil]

Don't know about the rubocop version, I don't remember when I touched it last time. However, I know that two days ago when I created PR #111 and pushed commit 3a696e9 rubocop test was okay (because I have a git-hook which verifies this) and it still is okay at that moment in time.

(system-3.6.9) halil@:~/dev/optimizer-api((HEAD detached at 3a696e9a))$ git checkout 3a696e9a2b0d56d5469759da82752732b784068f
HEAD is now at 3a696e9a Fix: eliminate negatif infeasible quantities
post-checkout hook is called
(system-3.6.9) halil@:~/dev/optimizer-api((HEAD detached at 3a696e9a))$ optim_test_rubocop 
Started with run options --verbose --seed 58700

  /0: [=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=] 0% Time: 00:00:00,  ETA: ??:??:??

RubocopTest#test_no_offenses_in_tests
  1/1: [========================================================================] 100% Time: 00:00:01, Time: 00:00:01

Finished in 1.05855s
1 tests, 1 assertions, 0 failures, 0 errors, 0 skips

[senhalil]

If I do bundle install in this branch Gemfile.lock changes.. @alain-andre is this the case if you do bundle install on your side? If that is the case, can you push that version of the Gemfile.lock?

[alain-andre]

If I do bundle install in this branch Gemfile.lock changes.. @alain-andre is this the case if you do bundle install on your side? If that is the case, can you push that version of the Gemfile.lock?

Yes you are right, I forgot to remove the gem limitations in lock file, I'm updating the commit.

[senhalil]

white-space typos otherwise 👌