[many ports] Add supports

[PhoebeHui]

Closes #12390 #12830 #11277 (comment)

Add unsupport arch/target to 'Support".

[Neumann-A]

Add unsupport arch/target to 'Support".

@ras0219 @ras0219-msft @strega-nil : I think the Supports field should only be used if a port is not designed to be used on a specific platform and not mean vcpkg is just not currently able to build the port on that platform. Maybe a clear guideline when /how to use the Supports field is required.

[BillyONeal]

We had an IRL discussion about this on Thursday. The results of that were:

• The Supports field is primarily intended to avoid folks needing to waste time building stuff that we know will be broken. To that end, it is an artifact of the port, not of the package, so if the port we have is unable to target a platform it doesn't matter what the package supports.
• The Supports field is not an artifact of our CI system, so if a port works locally but is broken in our CI system for some reason (e.g. conflicts with another port in a way we accept like boringssl, depends on some dependency already being installed we can't install there for some reason, etc) that goes in ci.baseline.txt, not Supports.

I believe this change is in keeping with those terms and thus good.

[PhoebeHui]

The I have added the !static to Supports for the 2 ports, however, it doesn't skip in CI, still failed here.

REGRESSION: alembic:x64-windows-static. If expected, add alembic:x64-windows-static=fail to .\scripts\ci.baseline.txt.
REGRESSION: avisynthplus:x64-windows-static. If expected, add avisynthplus:x64-windows-static=fail to .\scripts\ci.baseline.txt.

[BillyONeal]

The I have added the !static to Supports for the 2 ports, however, it doesn't skip in CI, still failed here.

vcpkg ci x64-windows-static for some reason isn't turning on the "static" flag when evaluating "supports" expressions. :(

[BillyONeal]

Thanks for your contribution!