Return the shell command that adds a package to the dcode tool env.
The result is built for execution (via perform_install_package), not for
display — surfacing raw uv tool invocations to the user is intentionally
avoided. package is validated here against PEP 508 grammar and then
shlex.quote-d by the shared builder: the validation already blocks shell
metacharacters, so the quoting is defense in depth that keeps the command
safe even if the pattern is later loosened.
Delegates to _uv_tool_install_command (the same builder the extras path
uses), passing the new package as a --with requirement. That builder folds
already-installed extras into the pinned deepagents-code[...] requirement,
and preserves the uv-managed Python interpreter and the receipt's existing
--with packages. Without this, reinstalling to add a second package would
replace the tool with a plain deepagents-code (dropping extras the user
added through /install <extra>), rebuild with only the newest --with
package (dropping previously configured custom providers), or silently
downgrade when the latest stable app depends on prerelease packages.
Like the extras path (_install_extra_uv_tool_command), passes
reinstall=True so the upgrade rebuilds the tool environment cleanly; see
_uv_tool_install_command's reinstall parameter for why an in-place
upgrade is unsafe.
Propagates ExtrasIntrospectionError if installed extras cannot be
determined safely from distribution metadata (or a metadata-sourced extra
name fails PEP 508 validation), and ToolRequirementIntrospectionError if
the uv tool receipt's interpreter or --with packages cannot be determined
safely.