Adding back "v" in order for the release to be found.

[pacostas]

Summary

This PR adds the "v" character in front of the release version, as otherwise, it is unable to find and publish it. Specifically on the below actions, the publish draft release action fails due to the "v" character being removed in order to do the ordering. Adding it back manages to find and publish the draft release.

Use Cases

Related issues to close after

• Failure: Publish draft releases paketo-community/ubi-nodejs-extension#160 (comment)
• Failure: Publish draft releases node-run-script#310
• Failure: Publish draft releases node-start#522
• Failure: Publish draft releases yarn-start#502
• Failure: Publish draft releases node-engine#937
• Failure: Publish draft releases npm-install#707
• Failure: Publish draft releases yarn#570
• Failure: Publish draft releases npm-start#504

Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
• I have added an integration test, if necessary.
• I have reviewed the styleguide for guidance on my code quality.
• I'm happy with the commit history on this PR (I have rebased/squashed as needed).

[sophiewigmore]

hi @pacostas, sorry for the bug I introduced! I already fixed this in #944 so I'm going to close this out