Invent compatibility check with ytsaurus server for ytop

[l0kix2]

We need some way to store supported yt versions in ytop code and some way of checking that image used in spec has correct version.
Preferably this should be done as soon as possible or at least before the cluster update in checkPossibility code.

[l0kix2]

1. If we try to fetch major version from user image:tag string — we can
   a) use it in validation webhook which is nice
   b) easy use it in reconilation flow to add checks which require version
   The problems here are
   a) we don't have contract for users to have images with version specified in tag and not sure if it is a good way (maybe compromise can be fetching version by default, but users can disable it with losing respective checks)
   b) maybe we need more fields like reign or smth which are not in image:tag string

2. If we try to run ytsaurus binary in job before update and fetch results from it — we need to invent a way to do that, because we don't have such jobs currently. Maybe configmap can be updated from job, maybe structured job logs can be used or some other solution.