I'm going through the CSP spec and trying to understand the treatment for the referrer field, and it doesn't seem to mention anything about adhering to the referrer policy of the page.
From logs, it appears chrome doesn't follow the referrer policy and adds the full referrer in the violation (including path and query parameters) even if the resource and referrer are cross origin. It also does the same thing if the CSP report endpoint is in a different origin as well.