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.

Start with the CLI runtime behavior described in the issue and the existing settings.json and copilot-instructions.md mechanisms. Determine how startupFiles patterns should be read and injected before the first model turn. Done means configured startup files are reliably loaded at session startup without requiring model compliance or a manual prompt.

Escrita pelo modelo de indexação a partir do texto da issue.