Config: Add framework and template_engine options

[marcoroth]

This pull request adds framework and template_engine configuration options to the .herb.yml.

These top-level settings tell Herb what environment it's running in and what template engine is being used for compilation. This enables context-aware behavior across the toolchain.

Configuration in .herb.yml:

framework: actionview      # ruby | actionview | hanami | sinatra (default: ruby)
template_engine: herb      # erubi | erb | herb (default: erubi)

Valid values are defined once in config/options.yml and code-generated into the relevant configuration files in all bindings.

This allows us in the future to have more specific features tailored for each target framework and engine. This pull request is meant to lay the groundwork for:

• Framework-aware linter rules, so that we can automatically enable/disable rules based on the framework (see Linter: Recommends Rails methods in a non-Rails project #480)
• Framework-aware compile-time optimizations. Knowing the framework context determines which helpers are available for optimization (like Engine: Compile-time optimizations for Action View tag helpers #1613)
• Template engine compatibility, surfacing invalid syntax or other target engine's conventions across the toolchain (for example no ERB block support, or future Herb-specfic features like Engine: <%# herb:security false %> directive #1161, Parser/Engine: ERB Block Comments Syntax #711, or similar)

[pkg-pr-new]

npx https://pkg.pr.new/@herb-tools/formatter@1658

npx https://pkg.pr.new/@herb-tools/language-server@1658

npx https://pkg.pr.new/@herb-tools/linter@1658

commit: a3f5a5d

[github-actions]

🌿 Interactive Playground and Documentation Preview

A preview deployment has been built for this pull request. Try out the changes live in the interactive playground:

• Playground Preview
• Documentation Preview
• Website Preview

---

_{🌱 Grown from commit a3f5a5d}

---

✅ Preview deployment has been cleaned up.