feat: add schema-driven Tailcall config generator

[poofeth]

Summary

/claim #373

Adds a schema-driven Tailcall configuration generator at /app/config.

This PR is intentionally broader than the current prototype in #595:

• loads the live Tailcall runtime JSON schema from generated/.tailcallrc.schema.json
• renders searchable schema-backed fields for server, upstream, and telemetry
• uses dropdowns for enums and booleans instead of free-text inputs
• supports repeatable @link entries
• exports JSON, YAML, and GraphQL config output
• provides copy and download actions with the correct file extension
• keeps the layout responsive across desktop and mobile breakpoints
• integrates the page through the regular Docusaurus Layout wrapper and page analytics

Validation

$ npm run build
[SUCCESS] Generated static files in "build".

$ npx prettier --check src/components/configGenerator/index.tsx src/pages/app/config.tsx
All matched files use Prettier code style!

$ git diff --check origin/develop...HEAD
# no output

npm run typecheck -- --pretty false still fails in existing repository areas unrelated to this PR: publish-externals/src/utils/hashnode.ts, src/components/playground/Playground.tsx, and the Algolia search theme files. The new config generator files are not part of those failures.

Notes

I saw the old issue thread included a design-hold comment. I kept the implementation close to the existing Tailcall visual system and used the current Tailwind tokens rather than introducing a separate visual language.

[poofeth]

/claim #373

[poofeth]

Fresh local validation from the current branch:

npm run build
# [SUCCESS] Generated static files in "build".

npx prettier --check src/components/configGenerator/index.tsx src/pages/app/config.tsx
# All matched files use Prettier code style!

Build emitted the existing optional ws dependency warnings for bufferutil / utf-8-validate, then completed successfully. Docusaurus also printed an update-check config-store permission notice after generation; it did not block the build.

[poofeth]

Closing this to keep my open review queue focused on active bounty paths. On review, the linked bounty issue appears to have been put on hold / already rewarded elsewhere, and there are newer duplicate PRs in flight. I do not want this PR to add noise for maintainers.