bump: add oras v1.2.0 to setup-oras

[wangxiaoxuan273]

Resolves #29

[shizhMSFT]

LGTM

[qweeah]

Since ORAS v1.2.0 are also released to FreeBSD and Linux ppc64le, riscv64 and s390x. Please

1. Add those new releases
2. Add corresponding parsing logic from node OS (see possible platform and arch) to supported release of ORAS.

https://github.com/marketplace/actions/cross-platform-action#supported-platforms

[shizhMSFT]

should this be ppc64le to match golang arch?

[wangxiaoxuan273]

Does it matter? My understanding is that this value is an internal map key, and we can use any value for it.

[wangxiaoxuan273]

changed to ppc64le

[shizhMSFT]

based on above comment, should this be ppc64le?

[wangxiaoxuan273]

changed to ppc64le

[qweeah]

LGTM

[qweeah]

I have validated the release.json using below script based on v1.2.0 checksum

#!/bin/bash

# Check if the correct number of arguments is given
if [ "$#" -ne 2 ]; then
	echo "Usage: $0 <checksum_file_path> <json_file_path>"
	exit 1
fi

# Assign arguments to variables
checksum_file="$1"
json_file="$2"

# Read each line in the checksum file
while IFS= read -r line; do
	# Extract the checksum, version, OS, and architecture from the line
	read -r sum file <<<"$line"

	# Split the file into VERSION, OS, and ARCH
	IFS='_' read -r _ version os arch <<<"$file"
	arch=${arch%%.*}
	
	# Use jq to extract the checksum from the JSON file for the corresponding version, OS, and architecture
	json_checksum=$(jq -r ".\"$version\".\"$os\".\"$arch\".checksum" "$json_file")

	# Compare the checksums
	if [ "$sum" == "$json_checksum" ]; then
		echo "Checksum MATCH for $file"
	else
		echo "Checksum MISMATCH for $file"
	fi
done <"$checksum_file"

[shizhMSFT]

LGTM