yay does not honor [N]one as response to clean build request

Affected Version

v13.0.1

Describe the bug

Regardless of whether "Enter" or "N" (for None) is entered in response to yay's asking for clean pkgbuild build choices, the PKGBUILD is still downloaded freshly into ~/.cache/yay/name_of_package.

As a result, when reviewing diff output in the next step (e.g., [A]ll), there is no longer a previous PKGBUILD file for comparison. And so all of the lines seen in the diff review are "+" green additions to a null older version.

Reproduction Steps

1. Repeated tests by three different users on multiple platforms testing different packages in the AUR have all produced the same results as described above.

Expected behavior

The request to refrain from cleanbuilding a package should be honored. And this should fix the diff results problem by preserving the older PKGBUILD, thereby allowing it to be used for diff comparison with the newly downloaded one - prior to any decision as to proceed with the package upgrade.

Output

See Above. Being able to review diffs has become especially important for safety given recent malware efforts attacking selected AUR packages.