tests: use rocksdb in the integration tests

[pedroferreira1]

Motivation

The next full node version will not support memory storage anymore and one of the nano contract indexes already doesn't support it. The main problem with using rocksdb is that the full node service takes more time to become healthy (with status port ready to receive requests), so the tx mining service and the test itself were breaking.

Then I created a healthcheck to validate if the node is already receiving http requests. I tried using curl or wget but the docker container doesn't have them installed, that's why it's using a python script to validate.

Acceptance Criteria

• Use rocksdb in the fullnode that runs in the integration tests

Security Checklist

• Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.02%. Comparing base (13f2b4d) to head (de702e9).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #819   +/-   ##
=======================================
  Coverage   81.02%   81.02%           
=======================================
  Files          91       91           
  Lines        7190     7190           
  Branches     1507     1517   +10     
=======================================
  Hits         5826     5826           
  Misses       1351     1351           
  Partials       13       13           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.