Implement MultiPayloadEnum support for projectEnumValue (#30635)

This code rearchitects and simplifies the projectEnumValue support by
introducing a new `TypeInfo` subclass for each kind of enum, including trivial,
no-payload, single-payload, and three different classes for multi-payload enums:

* "UnsupportedEnum" that we don't understand.  This returns "don't know" answers for all requests in cases where the runtime lacks enough information to accurately handle a particular enum.

* MP Enums that only use a separate tag value.  This includes generic enums and other dynamic layouts, as well as enums whose payloads have no spare bits.

* MP Enums that use spare bits, possibly in addition to a separate tag.  This logic can only be used, of course, if we can in fact compute a spare bit mask that agrees with the compiler.

The final challenge is to choose one of the above three handlings for every MPE.  Currently, we do not have an accurate source of information for the spare bit mask, so we never choose the third option above.  We use the second option for dynamic MPE layouts (including generics) and the first for everything else.

TODO: Once we can arrange for the compiler to expose spare bit mask data, we'll be able to use that to drive more MPE cases.

include/swift/Remote/RemoteAddress.h

@@ -47,6 +47,18 @@ public:
   uint64_t getAddressData() const {
     return Data;
   }
+
+  template<typename IntegerType>
+  RemoteAddress& operator+=(const IntegerType& rhs) {
+    Data += rhs;
+    return *this;
+  }
+
+  template<typename IntegerType>
+  friend RemoteAddress operator+(RemoteAddress lhs,
+                                 const IntegerType& rhs) {
+    return lhs += rhs;
+  }
 };
 
 /// A symbolic relocated absolute pointer value.