[Type refinement context] Don't query property wrappers just for range info

Querying property wrappers involves semantic analysis that can cause
cyclic references while building the type refinement context, and it's
unnecessary: we need only know that these are custom attributes to
incorporate their source ranges. Switch to the simpler/cheaper query.

A small part of fixing the cyclic references in rdar://112079160.

Author: DougGregor

lib/Sema/TypeCheckAvailability.cpp

@@ -679,13 +679,16 @@ class TypeRefinementContextBuilder : private ASTWalker {
       // For a variable declaration (without accessors) we use the range of the
       // containing pattern binding declaration to make sure that we include
       // any type annotation in the type refinement context range. We also
-      // need to include any attached property wrappers.
+      // need to include any custom attributes that were written on the
+      // declaration.
       if (auto *varDecl = dyn_cast<VarDecl>(storageDecl)) {
         if (auto *PBD = varDecl->getParentPatternBinding())
           Range = PBD->getSourceRange();
 
-        for (auto *propertyWrapper : varDecl->getAttachedPropertyWrappers()) {
-          Range.widen(propertyWrapper->getRange());
+        for (auto attr : varDecl->getOriginalAttrs()) {
+          if (auto customAttr = dyn_cast<CustomAttr>(attr)) {
+            Range.widen(customAttr->getRange());
+          }
         }
       }
 
@@ -696,7 +699,7 @@ class TypeRefinementContextBuilder : private ASTWalker {
       // locations and have callers of that method provide appropriate source
       // locations.
       SourceRange BracesRange = storageDecl->getBracesRange();
-      if (storageDecl->hasParsedAccessors() && BracesRange.isValid()) {
+      if (BracesRange.isValid()) {
         Range.widen(BracesRange);
       }