Expose configuration file path

[YevheniiSemendiak]

Why

Use-case from Synthesis team:

• create a batch action, which builds its own container image for it's tasks execution
• import this action into the batch
• the problem arises with the action portability

Conversation 1, conversation 2.

When one defines an image within the action, he should provide the path to its context and Dockerfile so the build could be executed. The problem is that Neuro-Flow renders all those paths as relative to the workspace root -- a folder within which a batch (not action) config resides.

This disables users from using batch actions with images, which could be built on-demand.

How

To resolve this issue, we could expose a path to the current configuration file in the workspace context. More details are here.