Rename SBOMs in Release to be backwards compatible with old installation instructions.

[bomoko]

Previous installation suggestions have us doing the following

RUN DOWNLOAD_PATH=$(curl -sL "https://api.github.com/repos/uselagoon/lagoon-sync/releases/latest" | grep "browser_download_url" | cut -d \" -f 4 | grep linux_386) && wget -O /tmp/lagoon-sync $DOWNLOAD_PATH && chmod +x /tmp/lagoon-sync

However, with the introduction of SBOMs into the build, this matches both the binary and the SBOM.

This necessitated us reconfiguring the install instructions to explicity ignore sboms - but some users are actually using the old installation instructions as part of their build process. The SBOM introduction thus breaks their build, as the grep command above matches both the binary and SBOM and then the command.

Before releasing anything > v0.8.2, we need a solution that is backwards compatible.