[metrohash] support more triplets by excluding 128 CRC source

[luncliff]

What does your PR fix?

Make metrohash support more triplets, which are not available because of _mm_crc32_u64 intrinsic

• Check VCPKG_TARGET_ARCHITECTURE to exclude source file that uses _mm_crc32_u64
• Lower the standard to C++ 11 so the compilers with lower versions can build this port.
• Minimize the CMake version constraint

Previous Work

• [metrohash] support iOS triplets #16035 (triplet support - iOS)
• [metrohash] support Android triplet build #15715 (triplet support - Android)

Which triplets are supported/not supported? Have you updated the CI baseline?

metrohash related failures are removed from ci.baseline.txt. ARM & UWP triplets become available because there is no more constraint of _mm_crc32_u64

• arm64-windows
• arm64-uwp
• x64-uwp

Does your PR follow the maintainer guide?

I thought we can create a patch for the header file, metrohash.h. It can add some macro checks like the following.

// ...
#ifndef METROHASH_METROHASH_H
#define METROHASH_METROHASH_H

#include "metrohash64.h" // <-- maybe we can replace "" to <> in the patch...
#include "metrohash128.h"
#if defined(_M_X64) || defined(__x86_64__)
// use SSE4.2 intrinsic _mm_crc32_u64
#include "metrohash128crc.h"
#endif
#endif // #ifndef METROHASH_METROHASH_H

I decided to remain simple for now but I'd like to hear about replacing vcpkg_replace_string with a patch like it.

[luncliff]

Feels like my team is the only one who is using this port 🤔

[PhoebeHui]

@luncliff, thanks for the PR!

@ras0219-msft, could you help further review?

[ras0219-msft]

Thanks for the PR!

I've pushed a change that includes @Hoikas's suggestion. @luncliff could you confirm that this still covers all your use cases?

[luncliff]

@ras0219-msft Thanks for the 1c8c750, I will check the port within days. :)

[luncliff]

Works as expected for x86-android, x64-android, x86-ios, and x64-ios. Great!