Remove bootstrap socket config after Ghost was started

[kirrg001]

Summary

With CLI 1.9 we have invented a new mechanism for systemd to figure out if Ghost is running or not.

CLI writes into the blog's config file, but doesn't clean up it afterwards (bootstrap-socket options)

If you then run ghost run the bootstrap socket options still exist and Ghost tries to connect to the socket. That is all fine, Ghost is just trying and stops after 3 tries, but it's very confusing.

If we remove the config, the CLI will add it next time ghost get's started/restarted.

Steps to Reproduce

1. Install Ghost on production using systemd
2. Start your blog
3. Stop your blog
4. run ghost run

Ghost-CLI: master