Reduce the amount of content included by <array>

[BillyONeal]

Resolves GH-462.

Made the following changes to have fewer dependencies from <array>:

• Demote back_inserter to <iterator>.
• Demote _Yarn to <xlocinfo>.
• Demote _Tidy_guard, _Tidy_deallocate_guard, and _Nothrow_compare to <xmemory>.
• Promote _Swap_ranges_unchecked to <xutility>.
• Change <array> to include only <xutility>.

This broke several real world code projects that only included <array> and called std::min or std::max. Therefore, the following workarounds were applied:

• Remove the _STL_ASSERT from std::min and std::max. We normally guard every op< with debug checks, but in this case we aren't using it to enforce something like a container invariant; the number of bad op<s we catch with it are likely microscopic.
• Delete _Min_value and _Max_value from <utility>.
• Move min and max to <utility> (in the exact position as the old _Min_value and _Max_value), except for the initializer_list overloads.
• Change all existing callers of _Min_value and _Max_value to call (_STD min) and (_STD max), respectively.

Checklist

• Identifiers in product code changes are properly _Ugly as per
  https://eel.is/c++draft/lex.name#3.1 or there are no product code changes.
• The STL builds successfully and all tests have passed (must be manually
  verified by an STL maintainer before automated testing is enabled on GitHub,
  leave this unchecked for initial submission).
• These changes introduce no known ABI breaks (adding members, renaming
  members, adding virtual functions, changing whether a type is an aggregate
  or trivially copyable, etc.).
• These changes were written from scratch using only this repository,
  the C++ Working Draft (including any cited standards), other WG21 papers
  (excluding reference implementations outside of proposed standard wording),
  and LWG issues as reference material. If they were derived from a project
  that's already listed in NOTICE.txt, that's fine, but please mention it.
  If they were derived from any other project (including Boost and libc++,
  which are not yet listed in NOTICE.txt), you must mention it here,
  so we can determine whether the license is compatible and what else needs
  to be done.

[BillyONeal]

Some of these changes might have to be scaled back depending on what comes back from the Microsoft-internal "RWC" test system. (That is, if too much real world code is broken)

[BillyONeal]

@ned14 I hope you're happy :)

[BillyONeal]

OK, results from RWC back:

• MongoDB needs a patch; they have some TU which wants std::min/std::max from somewhere they probably got from <array> before
• Pybind needs a patch, they have a header that wants std::min/std::max without <algorithm>.
  • Tensorflow needs a patch; they bundle Pybind
• Mysql needs patches, they want tie and stdint.h constants without including the right headers.
• Mame might need patches; they want ostream in some TUs, but RWC build before mine was unhappy with Mame so it might not be this change.

Investigating submitting upstream patches in these projects.

[BillyONeal]

Given that most of the projects are broken by min/max I'm going to make the following changes:

• Remove the _STL_ASSERT from std::min and std::max. We normally guard every op< with debug checks, but in this case we aren't using it to enforce something like a container invariant; the number of bad op<s we catch with it are likely microscopic.
• Delete _Min_value and _Max_value from <utility>.
• Move min and max to <utility> (in the exact position as the old _Min_value and _Max_value)
• Change all existing callers of _Min_value and _Max_value to call (_STD min) and (_STD max), respectively.