Enhance archiving documentation with event processing details

[marcpiechura]

Following up on our Discord discussion, I wanted to share this small addition to the documentation to help clarify the behavior of asynchronous projections when working with the Archived event.

There was at least one user who initially had the same misunderstanding, assuming that events appended to a stream would still be processed by asynchronous projections if they appear in the event sequence before the Archived event. That same user later solved the issue by using delayed messages, so I included this approach as one of the suggested workarounds.

[jeremydmiller]

@marcpiechura Another way to handle this would be to use RaiseSideEffects() to append the Archived event

[marcpiechura]

@jeremydmiller I actually added that as the first suggested option (“Writing the Archived event as a side effect within your asynchronous projection”), since you mentioned it during our Discord discussion.
Or did you mean a third option that I didn’t mention yet?

In the PR description, I just wanted to explain why I also included the delayed message option, because another user had used that approach successfully.