Set correct timeout flag in integration tests (eclipse-kanto#239)

[eclipse-kanto#238] Set correct timeout flag in integration tests

Signed-off-by: Antonia Avramova <[email protected]>

integration/testdata/remove-help.golden

@@ -13,6 +13,7 @@ Flags:
   -f, --force         Force stopping before removing a container
   -h, --help          help for remove
   -n, --name string   Remove a container with a specific name.
+  -t, --time string   Sets the timeout period to gracefully stop the container as duration string, e.g. 15s or 1m15s. When timeout expires the container process would be forcibly killed. If not specified the daemon default container stop timeout will be used.
 
 Global Flags:
       --debug         Switch commands log level to DEBUG mode

integration/testdata/stop-help.golden

@@ -13,7 +13,7 @@ Flags:
   -h, --help            help for stop
   -n, --name string     Stop a container with a specific name.
   -s, --signal string   Stop a container using a specific signal. Signals could be specified by using their names or numbers, e.g. SIGINT or 2. (default "SIGTERM")
-  -t, --time int        Sets the timeout period in seconds to gracefully stop the container. When timeout expires the container process would be forcibly killed. (default -9223372036854775808)
+  -t, --time string     Sets the timeout period to gracefully stop the container as duration string, e.g. 15s or 1m15s. When timeout expires the container process would be forcibly killed. If not specified the daemon default container stop timeout will be used.
 
 Global Flags:
       --debug         Switch commands log level to DEBUG mode