Use name as defined in ext/project_data.yaml rather than that provided b...

...y JIRA

This variable is defined for all projects. This will not change much,
except for where we have multiple projects under one JIRA project.
MCollective plugins is the prime example here. We have multiple plugins,
all with different names, but work is tracked under a single JIRA
project (MCOP). Because of this, the mcollective plugins, regardless of
which plugin is going to be released, all are assigned the same release
ticket title. This way, we can ensure the ticket title will be more
project specific, regardless of JIRA project.

It will not be as nice, for instance, when doing a Razor release, we
currently have `Razor 0.16.0 2014-11-24 Release`, but this will change
to `razor-server 0.16.0 2014-11-24 Release`.
You could include both here...something like:
```
summary = "#{Pkg::Config.project} (#{project_name})...
```

That would be noisier, but would give all of the information for a razor vs mcop release.