fix(ci): create the Cloudflare Pages project on the first deploy

[Bugs5382]

What and why

Closes #14

The first website deploy failed because the Cloudflare Pages project cryptos-pki-www didn't exist. Before the deploy, the Deploy workflow now lists the account's Pages projects (pages project list --json) using the same pinned cloudflare/wrangler-action. It runs pages project create cryptos-pki-www --production-branch=main only when the project is missing, so every later release skips that step. The secrets are unchanged and nothing new is printed. The README deploy section and docs/deploy.md now say the workflow creates the project, and that the custom domains are still attached once by hand in Cloudflare.

Verification

• actionlint passes.
• The project check was run locally against three sample outputs: an empty list (missing), a list with wrangler's banner ahead of the JSON array (found), and a list with another project only (missing).
• The Project Name key matches wrangler 4's pages project list --json output.

How this was verified

Locally with actionlint and the sample outputs above. The real path runs the next time a website release is published.