docs: clean up redundant Copilot instructions (#540)

The `.github/copilot-instructions.md` file contained setup instructions
that duplicated the automated setup already provided by
`copilot-setup-steps.yml`. This created confusion and unnecessary
maintenance overhead.

## Changes Made

**Removed redundant setup sections:**
- Eliminated manual environment setup instructions (Python, uv,
pre-commit, pyright installation)
- Removed the entire "Copilot Agent Environment Setup" section that
duplicated automated setup
- Simplified the "Bootstrap, Build, and Test" section to focus on usage
rather than setup

**Updated documentation to reflect automated setup:**
- Modified environment setup instructions to simply reference activating
the pre-configured virtual environment
- Updated troubleshooting section to reflect that tools are
pre-installed
- Revised development notes to mention the pre-configured environment

**Preserved essential information:**
- Kept all usage instructions for running tests, linting, type checking,
and building documentation
- Maintained CLI usage examples and validation steps
- Preserved timing information and troubleshooting guidance

## Impact

The instructions now accurately reflect that the Copilot environment
automatically sets up all necessary tools, eliminating redundancy while
maintaining all essential information for developers. This reduces
confusion and ensures the documentation stays in sync with the automated
setup process.

Fixes #539.

> [!WARNING]
>
> <details>
> <summary>Firewall rules blocked me from connecting to one or more
addresses (expand for details)</summary>
>
> #### I tried to connect to the following addresses, but was blocked by
firewall rules:
>
> - `docs.deepmodeling.com`
> - Triggering command:
`/home/REDACTED/work/dpdispatcher/dpdispatcher/.venv/bin/python3
/home/REDACTED/work/dpdispatcher/dpdispatcher/.venv/bin/sphinx-build -M
html . _build` (dns block)
> - `docs.python.org`
> - Triggering command:
`/home/REDACTED/work/dpdispatcher/dpdispatcher/.venv/bin/python3
/home/REDACTED/work/dpdispatcher/dpdispatcher/.venv/bin/sphinx-build -M
html . _build` (dns block)
>
> If you need me to access, download, or install something from one of
these locations, you can either:
>
> - Configure [Actions setup
steps](https://gh.io/copilot/actions-setup-steps) to set up my
environment, which run before the firewall is enabled
> - Add the appropriate URLs or hosts to the custom allowlist in this
repository's [Copilot coding agent
settings](https://github.com/deepmodeling/dpdispatcher/settings/copilot/coding_agent)
(admins only)
>
> </details>



<!-- START COPILOT CODING AGENT TIPS -->
---

💡 You can make Copilot smarter by setting up custom instructions,
customizing its development environment and configuring Model Context
Protocol (MCP) servers. Learn more [Copilot coding agent
tips](https://gh.io/copilot-coding-agent-tips) in the docs.

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: njzjz <[email protected]>

Author: Copilot

.github/copilot-instructions.md

@@ -8,14 +8,10 @@ Always reference these instructions first and fallback to search or bash command
 
 ### Bootstrap, Build, and Test
 
-- **Create virtual environment and install:**
+- **Environment setup:** The Python environment, `uv`, `pre-commit`, and `pyright` are automatically set up by the Copilot environment. Simply activate the virtual environment:
 
   ```bash
-  uv venv .venv
   source .venv/bin/activate
-  uv pip install .[test] coverage
-  uv tool install pre-commit
-  uv tool install pyright
   ```
 
 - **Run the test suite:**
@@ -55,24 +51,6 @@ Always reference these instructions first and fallback to search or bash command
 
   - **TIMING: Documentation build takes ~14 seconds.**
 
-### Copilot Agent Environment Setup
-
-Following GitHub's Copilot agent environment guidelines, this project uses:
-
-- **`uv`** for Python environment and dependency management
-- **`uv tool install`** for development tools (`pre-commit`, `pyright`)
-- **`pre-commit`** for automated code quality checks (preferred over direct tool usage)
-
-```bash
-# Initial setup
-uv venv .venv
-source .venv/bin/activate
-uv pip install .[test] coverage
-uv tool install pre-commit
-uv tool install pyright
-pre-commit install --install-hooks
-```
-
 ### CLI Usage
 
 - **Test basic CLI functionality:**
@@ -177,18 +155,18 @@ dpdisp run examples/dpdisp_run.py
 
 ## Development Notes
 
-- **Always use virtual environments** - The system Python is externally managed
+- **Virtual environment is pre-configured** - The environment is automatically set up; simply activate with `source .venv/bin/activate`
 - **Always add type hints** - Include proper type annotations in all Python code for better maintainability
 - **Always use conventional commit format** - All commit messages and PR titles must follow the conventional commit specification (e.g., `feat:`, `fix:`, `docs:`, `refactor:`, `test:`, `chore:`)
 - **Test artifacts are gitignored** - Job execution creates temporary files that are automatically excluded
-- **Pre-commit hooks available** - Use `pre-commit install --install-hooks` to enable automated code quality checks
+- **Pre-commit hooks are ready** - Pre-commit is pre-installed and hooks are configured
 - **Multiple execution contexts** - Code supports local execution, SSH remote execution, and various HPC schedulers
 - **Extensive examples** - Use `examples/` directory as reference for proper configuration formats
 
 ## Troubleshooting
 
-- **Virtual environment issues:** Always use `uv venv .venv` and `source .venv/bin/activate`
-- **Tool installation:** Use `uv tool install pre-commit` and `uv tool install pyright` for dev tools
+- **Virtual environment issues:** The virtual environment is pre-created; simply activate with `source .venv/bin/activate`
+- **Development tools:** `pre-commit` and `pyright` are pre-installed and ready to use
 - **Test failures:** Most tests run locally; some require specific HPC environments and will be skipped
 - **Documentation build warnings:** Some warnings about external inventory URLs are expected in sandboxed environments
 - **Pre-commit network issues:** If pre-commit fails with network timeouts, run `ruff check` and `ruff format` directly