[BUG] confusing "barrier finished" logging

[mlubin]

Example log:

Running concurrent (showing only PDLP log)

   Iter    Primal Obj.      Dual Obj.    Gap        Primal Res.  Dual Res.   Time
      0 +4.09965862e+10 +4.09965862e+10  0.00e+00   2.59e+08     5.48e+06   100.321s
   1000 -2.34924987e+11 -6.73488362e+10  1.68e+11   1.58e+06     4.29e+03   115.069s
   2000 -8.40723923e+10 +8.72057892e+10  1.71e+11   6.12e+05     4.95e+03   126.840s
   3000 -3.28011159e+10 +2.73515278e+11  3.06e+11   5.12e+05     6.65e+03   138.617s
   4000 -1.50528082e+10 +5.59259062e+11  5.74e+11   4.69e+05     1.33e+04   150.501s
   5000 -1.13325240e+10 +7.97759564e+11  8.09e+11   4.09e+05     1.21e+04   162.267s
Barrier finished in 172.47 seconds
   6000 -7.12409293e+09 +1.17012873e+12  1.18e+12   3.67e+05     1.99e+04   174.173s
   7000 -5.38506025e+09 +1.43439595e+12  1.44e+12   3.11e+05     1.78e+04   185.931s
   8000 -4.94612258e+09 +1.59818813e+12  1.60e+12   2.47e+05     1.57e+04   197.689s
   9000 -4.18304389e+09 +1.71912723e+12  1.72e+12   1.98e+05     1.56e+04   209.462s
  10000 -4.09659102e+09 +1.80577973e+12  1.81e+12   1.48e+05     1.37e+04   221.223

In this instance, "Barrier finished" actually means that barrier failed because it ran out of memory. We should log why barrier finished also.