Add `nodejs` to the `Environments` Protocol type signature

The Environments.create() Protocol in src/posit/connect/environments.py lists explicit keyword arguments for python, r, quarto, and tensorflow installations, but not nodejs.

Connect is adding support for nodejs.installations as an option for execution environments.

• POST /v1/environments accepts it
• PUT /v1/environments/{guid} also accepts it
• and GET always returns it.

At runtime the underlying _ResourceSequence.create(**attributes) happily POSTs a nodejs=... kwarg, so the SDK works against the new field today.

The gap is purely typing: static type-checkers and IDE autocomplete flag nodejs=... as unexpected.

Suggested change

Add nodejs: Installations | None = ... alongside the other language kwargs in three places in src/posit/connect/environments.py:

• Environment.update
• Environments.create
• Environments.find_by

Node.js content support is currently behind EarlyAccess.NodeJs` in Connect, but the field shape mirrors the other languages exactly.

Read the Environments protocol definitions in src/posit/connect/environments.py, focusing on Environment.update, Environments.create, and Environments.find_by and their existing installation arguments. Add the nodejs parameter consistently, then run the project's type checks or tests to confirm nodejs is accepted by static tooling in all three entry points.