Check DB sizes and trimming procedure

[krzysiekfonal]

We should verify how exactly it is configured and why WAL file is not decreasing but grows constantly much faster than DB file, at least over oplimit network.
DB file takes about 1.1GB while WAL ~80GB.

[krzysiekfonal]

@krzysiekfonal will first verify the same happens on fresh netowrk like Kaolin, then if issue is really there we will assign it to someone and prioritize it.

First, python-sdk needs to be updated (and oplimit network needs to be redeployed with the newest state)

[krzysiekfonal]

I redeployed oplimit from scratch making sure it operates on the newest opgeth and bitmap-sqlite-storage.
Problem has gone, so there were no real issue but somehow oplimit network still contained bi-temporal based on opened transactions.
At the time of writing it DB has 114k payloads in DB reached 1GB (before DB had 1.1GB while WAL had 90GB):

/ # ls -lhs state/
total 997M
      0 drwx------    4 root     root          87 Mar  6 14:27 geth
      0 srw-------    1 root     root           0 Mar  6 13:27 geth.ipc
 985.2M -rw-r--r--    1 root     root      985.2M Mar  6 15:26 golem-base.db
  32.0K -rw-r--r--    1 root     root       32.0K Mar  6 15:25 golem-base.db-shm
  11.6M -rw-r--r--    1 root     root       11.6M Mar  6 15:26 golem-base.db-wal