lib: document remaining ProxyHandler trap parameters

[Yogesh Kumar (yogesh968)]

ProxyHandler documents target on every trap, but several traps stop there and leave
their remaining parameters undocumented, so hovering them in an editor shows a parameter
list with no descriptions attached. One trap documents a parameter that does not exist.

Trap	Problem
apply	thisArg and argArray undocumented
construct	argArray undocumented (target and newTarget are documented, so it is skipped in the middle)
defineProperty	property and attributes undocumented
set	newValue undocumented (target, p and receiver are documented)
setPrototypeOf	documents @param newPrototype, but the parameter is named v

The setPrototypeOf one is the reason the others are worth fixing together: because the
JSDoc name does not match the parameter, the description is dropped on the floor and the
parameter shows up bare, exactly like the undocumented ones.

For that trap I renamed the parameter v → newPrototype rather than renaming the tag,
for two reasons. The neighbouring set trap already spells its value parameter
newValue instead of the spec's V, so newPrototype is what matches the surrounding
file; and the existing JSDoc shows newPrototype was the intended name. This follows
#63504, which renamed maxLength/fillString to targetLength/padString for the same
kind of mismatch. Parameter names in a .d.ts do not participate in assignability, so
this does not change what type-checks — it changes the name shown in completions and
signature help.

The added descriptions follow the wording already used by the sibling traps in this file
(The name or Symbol of the property to ...).

Testing

npx hereby runtests-parallel — 106,369 passing, no baseline changes from this PR.
(The full run was done with this change alongside three other lib JSDoc fixes I am
sending separately; the only baselines it moved belong to the [Symbol.matchAll]
parameter rename in that other PR, not to this one.)

Disclosure

This patch was authored with AI assistance (Claude Code). I chose the change, reviewed the
diff, ran the tests locally, and will be the one responding to review feedback.

[typescript-automation]

This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise.

[typescript-automation]

This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise.

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.