docs: standardize endpoint reference sections

[hrishabhayush]

What changed

• Normalized endpoint paths for single-resource routes:
  • GET /v1/deployments/{dseq}
  • PUT /v1/deployments/{dseq}
  • DELETE /v1/deployments/{dseq}
• Reworked endpoint sections to a consistent structure:
  • purpose sentence
  • parameters table
  • cURL example
  • JavaScript (fetch) example
  • response schema table
  • example JSON response
• Updated all listed Console API endpoints in this reference to follow the same template style.

Why

• Make the reference predictable and faster to scan.
• Reduce integration errors from inconsistent path/parameter documentation.
• Improve copy-paste usability by giving complete request/response examples for each endpoint.

Test plan

• Run docs locally from worktrees/wt-api-endpoints.
• Open /docs/api-documentation/console-api/api-reference/.
• Verify /v1/deployments/{dseq} paths render correctly for GET/PUT/DELETE.
• Verify each endpoint section includes parameters, cURL, JS, and response examples.
• Spot-check v1 and v2 endpoint formatting consistency.

[hrishabhayush]

Is there something related to staking link broken in CI/CD which is affecting my PR?

[hrishabhayush]

Can't seem to merge it even after approval @baktun14.