Avoid misleading enabled profiler log when it fails

We've mistakenly removed a return that would avoid logging a successful message when trying to start the go profiler (and it fails).

Tests were updated to catch that only the right logs are written.