Refactor: Layered design for `block` package

The block package is a model(or schema) of DataBase.
Hence, The block package should not depend on any other packages except common and storage.
But other packages use it as a data entity.
If it is accepted, packages are more loose coupling high cohesion
And then, followings are possible

- Move finishOperationXXX functions from `checker` to operation method
- ...

No files or tests are named. Start by tracing the block package's imports and its use by checker, then review the finishOperationXXX functions and the common and storage packages. Done means the intended dependency boundary and operation placement are agreed and implemented, with affected tests passing.

Written by the indexing model from the issue text.