fix: remove the NO-CSRF-CHECK header
This header is not handled by the cubicweb. It was added as a potential solution to differentiate web clients from other consumers (Node or python client). But the chosen solution is to use an actual CSRF-TOKEN.
Closes #5 (closed).