slap/standalone: let standalone's supervisord control instance supervisord

Instead of letting slapos commands start supervisord in daemon mode, run it
as a program from standalone supervisord daemon.

The $INSTANCE/etc/supervisord.conf will be created by `slapos node instance`
the first time user runs it, until this, the service will restart in a loop,
complaining that config file is not found.

Also review stop to expose timeout argument and use a longer timeout by
default (and cleanup some unused imports).
Status Job ID Name Coverage
  External
passed SlapOS.Eggs.UnitTest-Jerome.Python2

00:12:36

passed SlapOS.Eggs.UnitTest-Jerome.Python3

00:12:31

running SlapOS.SoftwareReleases.IntegrationTest-Jerome-Python2-feat/standalone-foreground

34369:16:36

passed SlapOS.Eggs.UnitTest-Jerome.Python2

00:21:16

passed SlapOS.Eggs.UnitTest-Jerome.Python2

00:11:29

passed SlapOS.Eggs.UnitTest-Jerome.Python2

00:10:15

passed SlapOS.Eggs.UnitTest-Jerome.Python2

passed SlapOS.Eggs.UnitTest-Jerome.Python3

00:26:27

passed SlapOS.Eggs.UnitTest-Jerome.Python3

00:21:52

passed SlapOS.Eggs.UnitTest-Jerome.Python3

00:25:55

passed SlapOS.SoftwareReleases.IntegrationTest-Jerome-Python2-feat/standalone-foreground

09:48:01

failed SlapOS.SoftwareReleases.IntegrationTest-Jerome-Python2-feat/standalone-foreground

17:33:00