[Content collections] Load content config with full Vite setup

[bholmesdev]

Changes

• Resolves Cannot resolve aliased module from src/content/config.ts #5990
• Dev: Load content config with existing dev server, instead of creating a new one
  • Moves type generation to after dev server startup instead of before
  • Ensures [content] logs happen after server port logs, which should make them more visible
• Build: Load config by calling the astro sync command internally, with full createVite result instead of condensed config

Testing

Ensure existing tests still pass

Docs

N/A

[changeset-bot]

🦋 Changeset detected

Latest commit: 6a7cf2b

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[matthewp]

Very clean design! Nicely done.

[bholmesdev]

Circling back to that failing unit test tomorrow. I discovered the renderentry configs weren't getting loaded previously because it used an invalid config format (schema: { instead of schema: z.object({). Fixing this, it looks like the layout test fails when the config is present. The test passes if I remove the config.ts mock 🤷