Elements. Set fragment offsets only using InformativeDataApplier, not in FragmentBuilder.

This way, there will be only one implementation, which will not get
out of sync with another implementation. This also makes FragmentBuilder
simpler and more cohesive.

Change-Id: I79727f549bba489be324f8ab1fdc61a9b3948cab
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/440001
Reviewed-by: Samuel Rawlins <[email protected]>
Commit-Queue: Konstantin Shcheglov <[email protected]>

Author: scheglov

pkg/analyzer/lib/src/dart/analysis/driver.dart

@@ -109,7 +109,7 @@ testFineAfterLibraryAnalyzerHook;
 // TODO(scheglov): Clean up the list of implicitly analyzed files.
 class AnalysisDriver {
   /// The version of data format, should be incremented on every format change.
-  static const int DATA_VERSION = 502;
+  static const int DATA_VERSION = 503;
 
   /// The number of exception contexts allowed to write. Once this field is
   /// zero, we stop writing any new exception contexts in this process.

pkg/analyzer/lib/src/dart/element/element.dart

@@ -10013,6 +10013,10 @@ class TypeAliasFragmentImpl extends _ExistingFragmentImpl
     aliasedElement?.enclosingElement = this;
   }
 
+  FragmentImpl? get aliasedElement_unresolved {
+    return _aliasedElement;
+  }
+
   /// The aliased type.
   ///
   /// If non-function type aliases feature is enabled for the enclosing library,