Readiness should not be "ok" if contents are not accessible

[tmm360]

Context

Bee 1.8.0, migrating from 1.7.0. The process isn't still completed

Summary

The node is not ready, because it is not able to serve data. This value is used, in my case, for understand if a node can be selected serving a request. This is an important issue, because this selection system doesn't work if readiness is always ok.

Expected behavior

It should be any other value instead.

Actual behavior

{
"status": "ok",
"version": "1.8.0-7b6c083c",
"apiVersion": "3.0.2",
"debugApiVersion": "3.0.2"
}

Steps to reproduce

Ask for readiness when node is migrating.

Possible solution

---

[istae]

in the case of the upcoming migration of the localstore rewrite, this should be taken into consideration.