Update CI release job once master in sync with develop

[mr-archano]

Problem

We have recently added the support for snapshot releases as part of #152, but we are missing that code in master. Next time we want to promote the current develop to be part of an official release the CI job (https://ci.novoda.com/job/no-player/) might fail as the release config has changed.

Potential Solution

Ideally we would change the CI job to use the secret properties file (already provided here) similar to what already done for the snapshot job.

Impact

Fixing the issue will allow us to correctly release a new version of the player without issues, and if follow the suggestion above we can start adopting the secrets files to avoid hidden credentials setup and promote explicit setup as part of the build scripts.

[Mecharyry]

@mr-archano I've updated the main job to use the secret properties file. Is it ok for us to close this issue now?

[mr-archano]

Yep, I think so: you must have addressed this before being able to release from master 👍