The concurrent logic of `ClientModeMultiProcessDebugger` extracted to `RecurrentTaskExecutor`. The connection logic is kept at `ClientModeMultiProcessDebugger`.

This is required to finish `RemoteDebugger` connections smoothly in `ClientModeMultiProcessDebugger` connection threads.

The connection strategy of "client mode" debugger reworked to meet local Python Docker Compose interpreter behavior. The `docker-compose` executable might start target Python script after a set of lengthy actions: building images, preparing network configuration, starting other services, etc. (technically we could use `docker-compose events` command to track this moment). Due to this property we need to try connecting repeatedly and effectively for a prolonged time with a reliable timeout.

The auxiliary method `DockerComposeProcessUtil.toRemoteProcess()` is going to be removed.

* introduce Master/Slave editors
* disable "Smart Zoom" in slave editors

* avoid changing size twice: at editor creation and when adding it
  into component hierarchy

* do not fire JComponent property changes on ImageFileEditorImpl

alternative fix, without passing additional parameter via UpdateParameterInfoContext

they don't seem to serve useful purpose, but complicate the logic
and prohibit PSI from properly functioning in default project

Also allow tracking traversal direction

= vue tags can have empty body and be self-closing
WEB-30808 Some of the vue components may have an empty body

update PostCSSPluginCheckTest, PluginTestCase