Add a new more complete unit test which emulates how Xamarin.Android uses LibZipSharp.

Also made a small change to the way we handle reading from a stream. According to the documentation stream.Read can return a value less than what was asked. So we need to keep reading until we get all the data we expected or an error is thrown.

* [ci] Use new EO compliant build pools

Context: https://eng.ms/docs/initiatives/executive-order/executive-order-requirements/executiveorderoncybersecurity/buildinfraops

Migrates to new build pools as part of ongoing security and compliance
efforts.

Bump vcpkg to the latest version.
Add support for building win-arm64 native libraries and add them to the Nuget Package.
Bump version to 2.0.4 and the Nuget to 2.0.4-alpha-1.

See https://docs.microsoft.com/en-us/dotnet/api/system.runtime.interopservices.architecture?view=net-6.0

Now that we ship an arm based native library on windows we need to be
able to determine the underlying library to load. We can use the
`RuntimeInformation.ProcessArchitecture` value to get this data.

Then based on that we can load from `x86`, `x64` or `arm64` subdirectories.
Note we will still fallback to loading from the current directory , but
the preference is to load from on of the architecture specific sub directories.