Incorrect position of error reported from macro in inline methods chain

This issue is based on scalameta/metals#3214

The position of error that was produced in inline context is unwrapped to the outermost one. In case if it’s a chain of inline calls, it’s unclear where the actual error happens.

Example:

// InlineMac.scala
object InlineMac:
  
  inline def sample(inline expr: String): Int =
    ${ sampleImpl('expr) }
  
  def sampleImpl(expr: Expr[String])(using Quotes): Expr[Int] =
      import quotes.reflect.*
      report.errorAndAbort("Error", expr)
      
// Main.scala
object Main:
  def main(args: Array: String): Unit =
     inline def v2 = InlineMac.sample("foo")  // <- the actual error position was here
     inline def v1 = v2
     
     v2  // [error] Error <- reported error position is here - wrong

There is a difference between in error message between direct compiler usage and using bsp-client. The default compiler reportee additionally adds lines like: This location contains code that was inlined from Main.scala:27 but I don’t think that it helps a lot in this case.

[dos65]

@tgodzik The plan was to extend the diagnostic structure to carry this additional info for inline error, but I haven’t had time to prototype this thing yet.

[deusaquilus]

Thanks for all your work @nicolasstucki, @dos65 and @tgodzik! Being able to display error underlines on specific terms is super exciting for me!