reproducible builds: scala 3 tasty differences in pekko-http-core `HttpEntity.tasty`

aside https://github.com/lampepfl/dotty/issues/17330 , I'm seeing differences in the tasty segments of Scala 3 artifacts.

`HttpEntity.tasty` seems to refer to different source paths:

```
source paths:
0: http-core/src/main/scala/org/apache/pekko/http/scaladsl/model/HttpEntity.scala
2063: http-core/target/scala-3.3.1/src_managed/HttpMessage.scala
```
vs
```
source paths:
0: http-core/src/main/scala/org/apache/pekko/http/scaladsl/model/HttpEntity.scala
2063: http-core/src/main/scala/org/apache/pekko/http/impl/engine/parsing/ParserOutput.scala
```

It's not clear to me whether/how those source paths are used.

Start by comparing the Scala 3.3.1 HttpEntity.tasty source-path entries shown in the issue, including the generated src_managed/HttpMessage.scala and ParserOutput.scala paths. Review the related Dotty issue and determine whether these paths affect reproducible artifacts; done means explaining the discrepancy and identifying a verified fix or documenting why it is harmless.

Written by the indexing model from the issue text.