tl;dr could we extend PackageManifest>>#isDeprecated to provide reasoning and
pointers to potential replacements?
I was loading some of my code into a Pharo7 image and while debugging noticed
that FileStream is deprecated (text stroke through in the Playground). But
neither the FileStream class comment nor the the ManifestDeprecatedFileStream
have an indication of what to use instead.
What do you think of making the deprecation notice carry more signal? E.g.
provide reasoning of why it was removed ("simplification", "no replacement for
XYZ", "Look at XYZ")?
