fix: document the flags the server actually requires

[lakhansamani]

Why

The setup line repeated verbatim in 11 READMEs predates two releases' worth of required flags. It does not merely lack --url — it fails before reaching it:

$ ./authorizer --database-type sqlite --database-url authorizer.db --admin-secret secret
Error: --encryption-key is required: no encryption key is set and --jwt-secret is empty ...

Adding --encryption-key then surfaces missing jwt type, then client ID missing in rootArgs, then --url is required. Four required flags missing in total.

What

Replaced with a command verified to boot against a build of authorizermain:

./authorizer \
--database-type sqlite --database-url authorizer.db \
--url http://localhost:8080 \
--jwt-type HS256 --jwt-secret <jwt-secret> \
--encryption-key "$(openssl rand -hex 32)" \
--client-id <client-id> --client-secret <client-secret> \
--admin-secret <admin-secret>

Also adds --url to with-org-saml and with-org-sso-oidc compose files and the with-k8s-tokenreview manifest. All three map 8080:8080, so the container's own address and the address the demo dials agree. All three validated as YAML.

Not changed: with-agent-permissions/run-server.sh and with-auth-recipes/run-server.sh already pass --url.

Related

• security(config): require --url, closing header-derived host takeover authorizer#764 made --url mandatory; #766 records it, #767 fixes the flag help
• fix(docs): correct nonexistent CLI flags and document --url as required docs#88 — the same sweep across the docs site