User should not be able to restart/stop config parse error builds

[jithine]

What happened:

Stopping a config parse error prevents a user from seeing the error in screwdriver.yaml parsing. And if user restarts the build it won't work unless some job in the screwdriver.yaml is main which is the dummy job used to represented yaml parse errors

What you expected to happen:

1. Users should always see config parse errors.
2. Alternatively redesign how config parse error can be displayed without having to build a dummy job
   1. We can add a new field in jobs model to store config parse errors

How to reproduce it:

1. Have a pipeline with config parse errors