Separate try-catch blocks for sessions

When going through all the sessions for checking if that annotation fits for their filters,
now the sessions have their own try-catch block, so if an exception arises in a session it will not affect other sessions.

Keeping the original try-catch block for the whole after_action() to, because an annotation with false document data could still
cause an exception before the session-loop starts, and we don't want any after_action() fail to affect any previous annotation activity (save, update, delete)