Component's code impovements

[l0kix2]

Component update flow is linear in nature, but it is not reflected in the component code.

More or less each component should have

1. separate initialization state optional jobs that are launched only once (though maybe simpler they be idempotent and can be launched on every component update)
2. update flow with pods recreation, optional post-update/migrate jobs, optional configuration from ytop code with yt client.

It should be possible to write component's code that way it would be seen what happens after what maybe with explicit separation of initialization stage.