BaseTools: Update nasm to 2.16.01

[makubacki]

Description

Fixes #11842

Updates the nasm ext dep to pick up the following fix:

Fix the invalid use of RELA–type relocations instead of REL–type
relocations when generating DWARF debug information for the elf32
output format.

---

Note: The 2.15.5 version currently used was pushed to the current NuGet feed at https://www.nuget.org/profiles/ProjectMu in February 2021. That feed has not been actively maintained since then. The nasm version is actively pushed to this feed now https://dev.azure.com/projectmu/mu/_artifacts/feed/Basetools-Binary/NuGet/mu_nasm/overview/20016.1.1.

Therefore, that is feed used to pull this update.

---

• Breaking change?
• Impacts security?
• Includes tests?

How This Was Tested

• CI

Integration Instructions

• No required action expected. Review the nasm release notes for more detail about the changes between nasm 2.15.5 and nasm 2.16.01.

[mdkinney]

Is there a reason the versioning scheme has changed?

[makubacki]

@kuqin12 made that change in 2023. He can comment on the details.

[kuqin12]

@mdkinney @makubacki

The versioning scheme was updated to include a wrapper version for the NuGet package itself, allowing multiple pushes for the same NASM version. In this approach:

• Major version of the NuGet package encodes NASM’s major and minor version. (nasm_major * 10000 + nasm_minor)
• Minor version represents the NASM revision number.
• Revision tracks the NuGet package’s own revision (number of pushes).

For example, NASM version 2.16.1 becomes 20016.1.x, where x increments with each push.

[makubacki]

Thanks @kuqin12. I'll include this info as a comment in the yaml file.

[makubacki]

Pushed the updated comment.

[mikebeaton]

Given the recent fix for nasm 3, I am just wondering what is the reasoning (or pre-existing planning?) for going incrementally and staying with 2?

[makubacki]

Given the recent fix for nasm 3, I am just wondering what is the reasoning (or pre-existing planning?) for going incrementally and staying with 2?

This PR is immediately addressing the fix requested in #11842

---

The nasm dependency has sat idle for a long time and there are multiple things that can be improved. I noted some of the more pressing issues here for follow up #11852.