Fix stale symbol errors connected to lazyvals

The actual stale symbol error, while recent, seems correct to me.
There is no reason why an earlier phase (Mixins) should see denotation
from a later phase (LazyVals) - if the opposite is true (like with the fix
here) the bringForward method is able to recover with a NoDenotation,
which is what we want.

compiler/src/dotty/tools/dotc/transform/LazyVals.scala

@@ -477,6 +477,7 @@ class LazyVals extends MiniPhase with IdentityDenotTransformer {
         newSymbol(claz, offsetName(info.defs.size), Synthetic, defn.LongType).enteredAfter(this)
       case None =>
         newSymbol(claz, offsetName(0), Synthetic, defn.LongType).enteredAfter(this)
+    offsetSymbol.installAfter(this)
     offsetSymbol.nn.addAnnotation(Annotation(defn.ScalaStaticAnnot, offsetSymbol.nn.span))
     val fieldTree = thizClass.select(lazyNme.RLazyVals.getDeclaredField).appliedTo(Literal(Constant(containerName.mangledString)))
     val offsetTree = ValDef(offsetSymbol.nn, getOffset.appliedTo(fieldTree))

tests/pos/i21271/Macro.scala

@@ -0,0 +1,12 @@
+import scala.quoted.*
+
+trait Schema
+object Schema:
+  lazy val sampleDate: String = "" // lazy val requried to reproduce
+
+  inline def derived: Schema =
+    annotations
+    new Schema {}
+
+inline def annotations: Int = ${ annotationsImpl }
+def annotationsImpl(using Quotes): Expr[Int] = Expr(1)

tests/pos/i21271/Test.scala

@@ -0,0 +1 @@
+val inputValueSchema = Schema.derived