CI: fix toolstate publishing

[Kobzol]

Toolstate publishing after something broke was not working (discovered here). The toolstate env. vars should only be needed for the publishing step, so I moved them there.

The toolstate script is also being checked in mingw-check on PR and auto CI, but it doesn't really seem to do anything, and it shouldn't require the token.

[rustbot]

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[ChrisDenton]

It's pretty impressive that toolstate has presumably been passing for years without a single failure

[Kobzol]

This was broken by my large CI restructuring that was finished ~2 weeks ago.

[ChrisDenton]

Ah! That makes more sense.

[Mark-Simulacrum]

@bors r+

[bors]

📌 Commit 7b6a3d0 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[bors]

⌛ Testing commit 7b6a3d0 with merge 84b9b6d...

[bors]

☀️ Test successful - checks-actions
Approved by: Mark-Simulacrum
Pushing 84b9b6d to master...

[rust-timer]

Finished benchmarking commit (84b9b6d): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

Results (primary -0.9%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-0.9%	[-0.9%, -0.9%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-0.9%	[-0.9%, -0.9%]	1

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 668.459s -> 669.294s (0.12%)
Artifact size: 316.25 MiB -> 316.25 MiB (0.00%)