Feature Request: Native startup files config in settings.json

## Problem

Users who maintain skill/reference files in `~/.copilot/skills/` need them loaded at the start of every session. Today the only mechanism is a prose instruction in `copilot-instructions.md` saying "read these files first" — but model compliance is inconsistent. 3 out of 3 new sessions this morning required manually prompting the agent to load skills.

## Proposed Solution

Add a `startupFiles` array in `settings.json` that the CLI runtime reads and injects into context automatically before the first model turn — no model compliance needed.

```json
"startupFiles": [
"~/.copilot/skills/**/*.md",
"~/.copilot/skills/references/*.md"
]
```

This would guarantee domain context is always present without wasting a turn on file reads or relying on the model to follow instructions.

## Impact

Any power user who builds custom skills, domain knowledge bases, or team-specific reference files hits this every single session. The current workaround is asking the agent "have you loaded skills" at the start of every session, which defeats the purpose of having persistent instructions.

Comienza con el comportamiento en tiempo de ejecución de la CLI descrito en el issue y con los mecanismos existentes de settings.json y copilot-instructions.md. Determina cómo deben leerse e inyectarse los patrones de startupFiles antes del primer turno del modelo. Se considera terminado cuando los archivos de inicio configurados se cargan de forma fiable al iniciar la sesión, sin requerir que el modelo cumpla las instrucciones ni un prompt manual.

Escrito por el modelo de indexación a partir del texto del issue.