[FEAT] Use release tag instead of latest on S3 to split up branch build results

[aptalca]

Is this a new feature request?

• I have searched the existing issues

Wanted change

Accept an env var RELEASE_TAG and use that value for S3 folder instead of a hardcoded latest here:

docker-ci/ci/ci.py

Line 686 in c8f7dca

latest_dir: str = f"{self.image}/latest"

That way results of different live branches can be in separate folders and can be linked in separate badges.

Reason for change

Currently, all live branch results are uploaded to S3 bucket into a latest folder. In the readmes, we link to the result in the latest folder. However, for images with more than one release tag, such as radarr (latest, development and nightly), the results from these 3 live branches are all mixed in, which leads to the master branch readme showing a badge linking to the latest of those 3, rather than linking to the result of that branch's latest build.

Proposed code change

I opened this PR for the jenkins-builder so that once the ci image pushes to dedicated folders on S3, the readmes can link to the correct latest result for that specific branch: linuxserver/docker-jenkins-builder#279

Ci image needs to be updated first. Updating ci won't really break anything. It's just that all branch readmes will show the master/main build results until updated by the jenkins builder after linuxserver/docker-jenkins-builder#279 is merged