Consider removing/reducing 64-bit prefix warnings

[qwertychouskie]

Back when the 64-bit warnings were added, things working properly with a 64-bit prefix were more the exception than the norm, and most applications worked just fine on 32-bit systems. Nowadays, many (if not most) applications only work on 64-bit systems, and most of the commonly used verbs have been updated to work properly in 64-bit prefixes.

Rather than always showing a 64-bit warning, perhaps it would be more advantageous to only show the warning for verbs with partial/missing 64-bit support. I propose adding a field to w_metadata called 64bit_support that has a few possible options:

• broken: verb completely broken in a 64-bit prefix
• missing: verb will install, but only install 32-bit versions of the DLLs
  • Example: msxml3 before https://github.com/Winetricks/winetricks/pull/2176
• partial: verb will install, but some components may be missing/inoperable in a 64-bit prefix
  • Example: msxml3 after https://github.com/Winetricks/winetricks/pull/2176 because for the resources DLL (msxml3r.dll), only the 32-bit version is installed
• full: Verb fully supported in a 64-bit prefix. For DLLs, this means all DLLs have both the 32-bit and 64-bit version installed. For apps, this means the app works just as well in a 64-bit prefix as a 32-bit prefix
  • Example: crypt32
• 64only: Verb only compatible with a 64-bit prefix

This has two main benefits

1. It gets rid of meaningless warnings
2. It makes the warnings that do remain actually mean something, which will also hopefully mean that more verbs get updated to fully support 64-bit prefixes, and therefore more applications can be easily ran on Linux.

Thoughts?