Meta: handle every notification from block

[carpawell]

Meta relies on order much. Object notifications were synced via raw block handling in #3219. Container creation and deletion are still done via separate subs channels.

Expected Behavior

Container PUT/DELETE can also be a part of the raw block handling and the order of object handling can be straight without any racing.

Current Behavior

Container drop is done via a separate routine as an optimization. (Un)subscription is our usual danger of neo-go's deadlock. Container creation and container removal may have a race.

Possible Solution

Use

neofs-node/pkg/services/meta/notifications.go

Lines 76 to 86 in 4f48532

	case h, ok := <-m.bCh:
	if !ok {
	err := m.reconnect(ctx)
	if err != nil {
	return err
	}
	continue
	}
	m.blockBuff <- h

for every notification (parsing logic may become a little more complex).

Steps to Reproduce (for bugs)

SearchV2 tests with fast container delete/create locked notifications and required kludges.