`<scoped_allocator>`, `<xpolymorphic_allocator.h>`: Pre-C++20 overload set of `construct` might be incorrect

Describe the bug
This program is well-formed in C++17 (but ill-formed since C++20 due to WG21-P0591), because the overload set of construct was specially designed for std::pair (N4659 [mem.poly.allocator.mem], cppreference).

#include <cstddef>
#include <memory_resource>
#include <type_traits>
#include <utility>

int main()
{
    std::pair<int, int> pr{};
    std::pmr::polymorphic_allocator<std::byte> pa{};

    pa.construct<int, int>(&pr);
}

However, MSVC STL always implements the C++20 overload set of construct, and hence rejects this program in C++17 mode (Godbolt link).

https://github.com/microsoft/STL/blob/73924c1920af92899f7582cd904ea819b9db35bc/stl/inc/xpolymorphic_allocator.h#L261-L270

scoped_allocator_adaptor::construct has exactly the same issue.

https://github.com/microsoft/STL/blob/73924c1920af92899f7582cd904ea819b9db35bc/stl/inc/scoped_allocator#L227-L239

The issue has been present even before implementing WG21-P0591 (#1668). I'm not sure whether this is a bug or an intentional design.

Additional context
LWG-3677 may be related to this if we want consistent behaviors in C++17 & C++20 modes.

Start with the C++17 reproducer and inspect the linked overloads in stl/inc/xpolymorphic_allocator.h and stl/inc/scoped_allocator. Compare their behavior with N4659, the cppreference description, and LWG-3677; done means the intended C++17 and C++20 behavior is established and verified for both allocator types.