Config parsing errors should include document + line context

[Deeven-Seru]

Title:
Config parse errors should include document + line/column

Prerequisites

• I searched the current open issues.

What are you trying to do that currently feels hard or impossible?

Quickly locate config errors in large multi‑doc YAML files.

Clear end goal (specific use‑case)

When the config is missing kind or name, I want the error to show doc index + line/column, so I can fix it without hunting.

Suggested Solution(s)

• Include doc index and line/column in errors from
  UnmarshalResourceConfig.
• If name is present but other fields are invalid, include the name in the
  error.
• Apply similar context to env‑var parsing errors.

Alternatives Considered

Manual search / binary search of YAML — not great.

Additional Details

Code pointers:

• internal/server/config.go → UnmarshalResourceConfig
• cmd/internal/config.go → ParseConfig / ConvertConfig