notification: properly handle cnx and lifetime of the hijacked session When we create a session for the notification rendering, we need to 1) give it a cnxset 2) commit and close it after we're done 3) restore the original session for subsequent notifications This changes the ordering of actual mail sending, since there are several different commits involved, but I don't see a way to fix that short of restoring hijack_user. Related to #2934523

/var/log/cubicweb/*.log {
        weekly
        missingok
        rotate 10
        compress
        delaycompress
        notifempty
        create 640 root adm
        sharedscripts
        postrotate
           if [ -x /usr/sbin/invoke-rc.d ]; then \
              invoke-rc.d cubicweb reload > /dev/null 2>&1; \
           else \
              /etc/init.d/cubicweb reload > /dev/null 2>&1; \
           fi; \
        endscript
}