Promote go-rpm-macros 3.6.0 to core repo in azure linux

[SumitJenaHCL]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?
This PR is to promote go-rpm-macros 3.6.0 to core repo in azurelinux.
We are adding new package ignition to core repo which is dependent on go-rpm-macros through PR #15516.

Change Log

• SPECS/go-rpm-macros/fixing_ldflags_for_azl.patch
• SPECS/go-rpm-macros/go-rpm-macros.signatures.json
• SPECS/go-rpm-macros/go-rpm-macros.spec

Does this affect the toolchain?

YES/NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• Pipeline build id: xxxx

[sandeepkarambelkar]

Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1032784&view=results

[sandeepkarambelkar]

Buddy Build successful.
No change promotion to base repo.
Changes LGTM.