What Causes "The operation couldn’t be completed. Undefined error: 0" Big Sur Defect?

A problem seems to exist with Big Sur Finder that can be discreetly identified when attempting to compress an application. The issue with the compression is not the actual problem but rather a symptom. When an application cannot be compressed and yields the following error:

("The operation couldn’t be completed. Undefined error: 0")

If this occurs, then a number of other Finder defect symptoms can be observed related to the given app. This is not a question about how to work around this defect in Big Sur, it is a question of "what causes this" and "can the macOS defect be avoided or fixed".

Some applications on Big Sur do not exhibit this issue, some do. The problem does not seem to be related to apps download from the web or from the App Store as it has occurred to apps that are sourced from both. (FinderMinder, open internet source. Apple Numbers, Pages, Keynote, App Store sourced).

The only way I have found to work around this is to obtain a copy of the app from some source that is not related to a macOS Big Sur storage volume. Unfortunately the problem seems to come back. I am not aware of any fix short of not using Big Sur. This problem occurred in the first release of Big Sur and is still occurring in 11.1. The applications were all present on the hard drive prior to loading Big Sur which suggests that the problem was created at the time of installation or after the launch of the file management system aka Finder.

The symptoms below relate to actions taken from a host MacBook Pro Touch Bar running Big Sur unless otherwise noted. When an application compression fails on the host, the other symptoms can be observed as noted. When an application does not fail to compress, the application then can be copied, moved, drug-dropped as expected and exhibit no errant symptoms.

Symptoms

Key:

Finder compress fails producing "The operation couldn’t be completed. Undefined error: 0"

Then:

1. Drag through Screen Sharing to copy to another machine always fails
2. Drag through Apple Remote Access (ARD) to another machine always fails.
3. Copy app from local HD to Apple File Protocol (AFP) server volume always works
4. Copy app from local HD to Server Message Block (SMB) file server volume fails
   1. Copy text file to same SMB volume works
5. Copy app to AFP volume, then to SMB volume from AFP volume will sometimes partially fails producing a corrupt app at the destination, other times just failing indicating "Items can’t be copied to “Sharing” because you don’t have permission to read them."
6. Deleting the partially failed copy fails with "The operation can’t be completed because the item “FolderColorizer” is in use."
7. Drag the copy from AFP server volume through Screen Sharing or ARD to another machine always fails the same way as #2
8. Compressing copy on AFP server sometimes works, sometimes fails the same as "Key"
9. Dragging compressed copy from server volume to anywhere else noted above with any mechanism always works
10. Decompressing the copy using any machine other than the source machine always fails with "Unable to expand "[appName]" into "[folderName]". (Error 1 - Operation not permitted.)
11. Decompressing the copy on the original (MacBook) will produced a corrupted copy of the app