docs: update copilot instructions to remove multipass and fix structure

- Remove Multipass references (not supported on GitHub shared runners)
- Fix duplicate Essential Principles section and missing emoji
- Remove duplicate project description paragraph
- Reorder sections for better logical flow (Project Overview before Essential Principles)
- Move Essential Principles before Essential Rules for better context
- Update virtualization provider references to use only LXD VM instances
- Maintain consistency with project's focus on LXD-based infrastructure

Author: josecelano

.github/copilot-instructions.md

@@ -1,29 +1,10 @@
-# ToThis is a deploymThese principles should guide all development decisions, code reviews, and feature implementations.
-
-## 🏗️ Tech Stack infrastructure proof-of-concept for the Torrust ecosystem. It uses OpenTofu (Terraform), Ansible, and Rust to provision and manage deployment environments with LXD containers and Multipass VMs.
-
-## 🎯 Essential Principles
-
-The development of this application is guided by fundamental principles that ensure quality, maintainability, and user experience. For detailed information, see [`docs/development-principles.md`](../docs/development-principles.md). Tracker Deploy - AI Assistant Instructions
+Tracker Deploy - AI Assistant Instructions
 
 ## 📋 Project Overview
 
-This is a deployment infrastructure proof-of-concept for the Torrust ecosystem. It uses OpenTofu (Terraform), Ansible, and Rust to provision and manage deployment environments with LXD containers and Multipass VMs.
-
-## � Essential Principles
-
-The development of this application is guided by fundamental principles that ensure quality, maintainability, and user experience. For detailed information, see [`docs/development-principles.md`](../docs/development-principles.md).
-
-**Core Principles:**
+This is a deployment infrastructure proof-of-concept for the Torrust ecosystem. It uses OpenTofu (Terraform), Ansible, and Rust to provision and manage deployment environments with LXD VM instances.
 
-- **Observability**: If it happens, we can see it - even after it happens (includes deep traceability)
-- **Testability**: Every component must be testable in isolation and as part of the whole
-- **User Friendliness**: All errors must be clear, informative, and solution-oriented
-- **Actionability**: The system must always tell users how to continue with detailed instructions
-
-These principles should guide all development decisions, code reviews, and feature implementations.
-
-## �🏗️ Tech Stack
+## 🏗️ Tech Stack
 
 - **Languages**: Rust, Shell scripts, YAML, TOML
 - **Infrastructure**: OpenTofu (Terraform), Ansible
@@ -51,6 +32,19 @@ These principles should guide all development decisions, code reviews, and featu
 - `cspell.json` - Spell checking configuration
 - `project-words.txt` - Project-specific dictionary
 
+## Essential Principles
+
+The development of this application is guided by fundamental principles that ensure quality, maintainability, and user experience. For detailed information, see [`docs/development-principles.md`](../docs/development-principles.md).
+
+**Core Principles:**
+
+- **Observability**: If it happens, we can see it - even after it happens (includes deep traceability)
+- **Testability**: Every component must be testable in isolation and as part of the whole
+- **User Friendliness**: All errors must be clear, informative, and solution-oriented
+- **Actionability**: The system must always tell users how to continue with detailed instructions
+
+These principles should guide all development decisions, code reviews, and feature implementations.
+
 ## 🔧 Essential Rules
 
 1. **Before creating branches**: Read [`docs/contributing/branching.md`](../docs/contributing/branching.md) for naming conventions (`{issue-number}-{short-description}`)