Secret Management: Change the default behaviour to wait for master password

Given that the default behaviour is to shutdown straight away when using a master password, the user experience here is not great. For example let's run through the following situation

• User has a power outage:
• User notice that Couchbase Server has not started and restarts it:

  sudo /etc/init.d/couchbase-server start

  Starting couchbase-server

  [ OK ]

• User sends the master password but gets the following error.

  $ sudo /opt/couchbase/bin/couchbase-cli master-password -c localhost:8091 --se

  nd-password

  Enter master password:

  Either the node is down or password was already supplied

• Given that Couchbase Server correctly started up as indicated by the green OK
• The user now checks and sees that CB has still not started
• User contacts support for help.

I think the end user would have a better experience if the Default behaviour of shutting down was changed to making it wait on startup.