feat(report): ruch przez wlasny token, zeby firma przestala pracowac na slepo - #231

…s working blind

The report has always said the traffic endpoints were out of reach. They are
out of reach for the Actions token specifically, and that got shortened over
time into "impossible", which is why nothing was done about it for weeks.

Verified against GitHub's documentation rather than recalled: the three traffic
endpoints need a fine-grained token carrying "Administration" repository
permissions, read. That is a token a person creates once.

It is read through a plain fetch with its own credential, not by setting it as
this step's github-token. Setting it there would be the obvious shortcut and it
would break the report: every write in the step would then act as the owner,
and GitHub does not notify the actor who performed an action, so the report
would quietly stop mailing the one person it is written for. That is red line 7
and it costs nothing to respect here.

Absent stays a supported state. Without the secret the report prints what it
printed before, now saying which secret is missing and what it costs: without
it the company builds pages without being able to see which ones bring anybody.

That is the actual reason this matters. Fourteen error pages went up today and
forty-eight URLs are indexed, and between one manual check and the next nobody
can tell which of them earn a visitor. A reach programme with no feedback loop
is a guess repeated on a schedule.