Introduce hard/soft limits for commiting run and run tool/pipeline

[SilinPavel]

Background
Docker images can be extremely big, so it is nice to have a mechanism to warn/reject user from creation or running such big images.

Approach

1. Let's introduce 2 new System preference - commit.container.size.limits, launch.tool.size.limits (Object) with structure:

   {
     "soft": <size value in bytes, long>,
     "hard": <size value in bytes, long>
   }
   

   Provide validation for the values of the properties`

2. Modify a method in PipelineRunController
   GET /run/{runId}/commit/check to provide more extended result like:

   {
       "enoughSpace": {
          "status": <ENUM (FAIL, WARN, OK)>,
          "message": <can be null, message in case of warning or fail>,
          "value": <raw value of the metric, for enoughSpace true/false>
       },
       "containerSize":  {
           "status": <ENUM (FAIL, WARN, OK)>,
           "message": <can be null, message in case of warning or fail>,
           "value": <raw value of the metric, for containerSize size in bytes>
       }
   }
   

   To do so, let's introduce new server method in DockerContainerOperationManager to be able to ask node which is host the run, current size of the run container.

   • This method should work similar as commit procedure (ssh to the node) and utilize command docker inspect ${CONTAINER_ID} -s --format "{{.SizeRw}}"
   • Timeout should be implemented for the method to not to hang much time
   • If something goes wrong (timeout or error) return -1 as containerSize

3. On UI:

   • During commit change logic to verify not only enoughSpace but also check that containerSize check status
     • If WARN:
       • Warn user that container image will be too big, but let to commit if needed
     • If FAIL
       • Restrict to commit
   • During Tool/Pipeline run, check if tool version size < system preference launch.tool.size.limits soft/hard
     • If bigger:
       • For soft : Warn user that container image is too big, but let to run if needed
       • For hard : Restrict to run

[NShaforostov]

Docs added via #3669 and located here and here.