ci: retire dead deploy-cli-docs Netlify job

[lokesh-vadlamudi]

What

Removes the deploy-cli-docs job from the Update CLI Docs workflow.

Why

That job published the CLI docs to the legacy Netlify site behind docs.lacework.net, which since the FortiCNAPP migration only 301-redirects to docs.fortinet.com/product/lacework-forticnapp. The Netlify site itself was decommissioned, so the job failed on every run:

GET https://api.netlify.com/api/v1/sites/$NETLIFY_SITE_ID/deploys
--> {"code":404,"message":"Not Found"}
jq: error (at <stdin>:1): Cannot index number with string "commit_ref"
Process completed with exit code 5

The 404 (site no longer resolves for the configured NETLIFY_SITE_ID) leaves the response as a {code,message} object, which the deploy script then fails to jq-parse. Example failing run: https://github.com/lacework/go-sdk/actions/runs/29549635816

CLI docs are now maintained on Fortinet's docs platform, so this deploy step has no valid target.

Scope

• Only the deploy-cli-docs job is removed (+ an explanatory comment left in its place).
• The update-cli-docs job is unchanged — it still generates the docs and commits them to lacework/docs_lw, which continues to feed the reader-redirect map (fortinet_redirects.py).