[SQUASH_ON_REBASE] Remove unused variable in DEBUG_CLEAR_MEMORY call

[kenlautner]

Description

In project MU we changed the DEBUG_CLEAR_MEMORY define to do nothing. This causes an issue in the new file MemoryAllocationLibPosix.c which calls it with a newly defined variable. To get around this variable is removed and instead we use what it was deriving its value from instead.

This should be merged with 230503 on a rebase

• Impacts functionality?
• Impacts security?
• Breaking change?
• Includes tests?
• Includes documentation?
• Backport to release branch?

How This Was Tested

Tested on the pipelines. No issues

Integration Instructions

N/A

[kenlautner]

@os-d are you okay with this type of change surrounding DEBUG_CLEAR_MEMORY or would you rather the macro have dummy functionality so we don't run into this problem in the future?

[os-d]

@os-d are you okay with this type of change surrounding DEBUG_CLEAR_MEMORY or would you rather the macro have dummy functionality so we don't run into this problem in the future?

I think just doing this here for now is okay, if it crops up again, we can look at it further. I would mark this [SQUASH_ON_REBASE] and in the commit message point to 2340503 to be squashed with.

I am starting to get some of the memory protections work upstreamed, so that should hopefully resolve this issue from spreading.

However, we probably have broken the ASAN on tests, or at least part of it, as it seems to be relying on this functionality.