no, see the pr on core: if we do this on the security context, things
only work if a firewall is configured on all routes that have a check.
this is the reason we still have a dedicated publish workflow checker
service. that checker is now modeled very closely to the security and
reusing that component where applicable. and integrated into it, so that
you could also inject the security.context if you are in a situation
where you do have a firewall.