Refactor logging component

[cthulhu-rider]

We use zap logger as a basis of app logger. Currently Logger type is an alias, but this does not seem desirable from the side of the application code. I propose to provide a specific API built on the built-in-Go and NeoFS-specific types, and close zap in the implementation. This will make it possible to complete the use of a wide range of zap features to those that are required specifically for our applications. Also, when changing zap API or switching to a new fundamental basis, the application code will not be affected.

The similar approach was performed for the config types based on viper.

[cthulhu-rider]

Also:

1. underline meaningful log messages (object lifetime, etc.)
2. per-component log (in config)

[cthulhu-rider]

In #1832 I was visited by the idea to unify some widely-used fields of the context. For example, provide

func FieldContainer(cnr cid.ID) Field {
  return FieldStringer("container", cnr)
}

func FieldEpoch(epoch uint64) Field {
  return FieldUint("epoch", epoch)
}

We can also add optional name string parameter to get field like "epoch (previous)": 100.

Also we can cover widely-used formats, e.g.

func FieldStringHex(name string, val string) Field {
  return FieldString(name, hex.EncodeToString(val))
}

func FieldStringBase58(name string, val string) Field {
  return FieldString(name, base58(val))
}

[roman-khimov]

Another proposal: drop pkg/util/logger, use zap and be done with it.

[cthulhu-rider]

lets use zap everywhere until other needs