*: deploy main chain NeoFS contract during setup, fix #296

[roman-khimov]

Not a lot of things to do here, but with this in place no dumps need to be created and you always have proper up-to-date NeoFS contract in dev-env, including development scenarios when you need to update it from some local copy.

Caveats:

• waiter is a trivial sleep, sufficient here, see https://github.com/nspcc-dev/neo-go/issues/3244
• .ir.env becomes dynamic, but it has to be present for docker-compose, see https://github.com/docker/compose/issues/3560
• processing contract is not deployed deliberately, it's useless for notary-less
• we will probably switch to notary-enabled when notary is no longer an extension