feat: show build and package management on the home page

[magnus-madsen]

The tooling comparison table further down the page claims that flix is its own build tool and package manager, but nothing on the page showed a manifest or what dependency resolution looks like.

Adds a section between Termination Checking and Built-in Test Framework, text-left / code-right.

What it shows

A flix.toml with package metadata, a Flix dependency from GitHub, and a JAR from Maven:

[package]
name        = "hello-world"
description = "A simple Flix package"
version     = "0.1.0"
license     = "Apache-2.0"

[dependencies]
"github:flix/museum" = "1.4.0"

[mvn-dependencies]
"org.apache.commons:commons-lang3" = "3.12.0"

and, stacked underneath it, what the next build prints:

Found `flix.toml'. Checking dependencies...
Resolving Flix dependencies...
  Downloading `flix/museum.toml` (v1.4.0)... OK.
  Downloading `flix/museum.fpkg` (v1.4.0)... OK.
Resolving Maven dependencies...
  Adding `org.apache.commons:commons-lang3' (3.12.0).
Dependency resolution completed.

Same two-block shape as the test framework section, so the pair reads as "the config, then what the tool does with it". The Maven coordinate is the same in both blocks so they agree.

Layout

The test framework row flips to code-left, which keeps the three rows alternating:

Section
Termination Checking	code left / text right
Build and Package Management	text left / code right
Built-in Test Framework	code left / text right

PlainSnippet

This is the third block on the page that is not Flix — terminal output twice, TOML once — and CodeSnippet only knows the Flix grammar, so it would colour all three as if they were code. The inline markup is now src/components/PlainSnippet.astro, and the test output added in #214 uses it too. No rendered change to that block; I checked all three still come out verbatim.

npm run check and npm run build both pass, and the new card is clear of the #212 inline-whitespace trap.

🤖 Generated with Claude Code