changed naming on upstart script for supervisorctl behavior

Not sure if you guys are having the same issues that I am with the pip instancing supervisor ...

details outlined here:
http://cuppster.com/2011/05/18/using-supervisor-with-upstart/

TLDR:
supervisorctl picks up /etc/init/supervisord.conf and attempts to use it as a supervisor configuration file **instead** of an upstart script


<pre>
$ salt '*' state.highstate
...

----------
          ID: supervisor-service
    Function: service.running
        Name: supervisor
      Result: False
     Comment: One or more requisite failed
     Changes:  

...
</pre>
The state ID here would be less brittle if it avoided platform-specific information. Perhaps `graphite_supervisord_conf` instead?