crofty 0.13.0 — clearer messages when analytics returns a 403

When crofty analytics got a 403 reading GA4 or Search Console, it didn’t say enough about which kind of error it was.

Before

It only said “grant access”.

After

It now names both possible causes:

• a wrong (or non-existent) property id
• the service account lacking access

On top of that, it prints Google’s own error message verbatim. For an AI, it returns a structured error under --json (cause, the property tried, a suggested next step).