Fix use case of `bosh-deploy-with-created-release` task

[svkrieger]

What is this change about?

The bosh-deploy-with-created-release task did not seem to work with a release tarball. The bash script was looking for a final.yml in the config folder, which is both not present when providing the release as a tarball.

I added two input parameters to the task: RELEASE_NAME_OF_TARBALL, which is the name of the release, which has been provided as a tarball and RELEASE_VERSION_OF_TARBALL, which is the version of that release. Both is needed to construct the ops file, to add the release to the deployment.yml.

The shared function bosh_interpolate needed some changes as well, to support the new version parameter.

Please provide contextual information.

I found #96, which also mentions about this problem, which seems to have never been fully resolved.

Please check all that apply for this PR:

• [ ] introduces a new task
• [x] changes an existing task
• [ ] changes the Dockerfile
• [ ] introduces a breaking change (other users will need to make manual changes when this is released)

Did you update the README as appropriate for this change?

• [ ] YES
• [x] N/A

How should this change be described in release notes?

Fixed use case of bosh-deploy-with-created-release task, where a release has been provided as a tarball.

What is the level of urgency for publishing this change?

• [ ] Urgent - unblocks current or future work
• [x] Slightly Less than Urgent