Record why a cool-tech-jobs submission failed - #20986

Fixes #20955

A company reported it could not submit the form on /cool-tech-jobs, and there was nothing left behind to look at. Three reasons, all in the same handler:

• A missing profile id or JWT returned silently. if (!profileID || !jwt) return stopped the submit with no message, so an expired session looked exactly like a broken page.
• Four different failures shared one catch and one message — create, logo upload, attach logos, scrape jobs — with no record of which one happened.
• That catch logged nothing and sent no event. A failure left no trace at all, which is why the report could not be acted on.

This tracks step as the handler moves through it, puts the step and the HTTP status into the thrown error, and on failure writes a console.error and captures cool_tech_jobs_submit_failed with the step. The expired-session case now says so, and tells the person their input is still there.

The message a user sees for a genuine failure is unchanged — this only adds what happens behind it.

cool_tech_jobs_submit_failed { step: 'create_company', message: 'create_company: 403 Forbidden' }
cool_tech_jobs_submit_failed { step: 'auth', reason: 'missing_jwt' }

I used usePostHog() and posthog?.capture(...), which is what IssueForm in this same file already does.

What I could not verify: I did not run the full site build, so this is checked by reading rather than by loading the page. npx prettier@2 --write on the file produces no changes, matching the version in package.json. If you would rather the event name or the property shape followed a different convention, say which and I will change it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01AqD13QkB8DhzkDSdKbJScv