SI-8719 pattern expander errors and warnings now go through context

This ensures that typechecking custom unapplications in silent mode
doesn't leak uncatchable errors. Interestingly enough, the problem
only manifested itself for custom unapply methods, not for synthetic
ones generated for case classes.
Are you suggesting to use the `isPastTyper` check in the error reporting portion of `alignPatterns`?