chore(deps): bump dependencies to their latest versions

[yollu]

Bumps all dependencies in the templates (and their generated counterparts) to the latest stable versions. Dependabot doesn't support cargo-generate templates, so this is the manual refresh requested in #91.

What changed

Versions bumped across every */template/Cargo.toml and the matching *-generated/Cargo.toml:

crate	from	to
ratatui	0.30.0	0.30.2
crossterm	0.28.1	0.29.0
tokio	1.40.0	1.52.3
clap	4.5.20	4.6.1
color-eyre	0.6.3	0.6.5
config	0.14.0	0.15.25
directories	5.0.1	6.0.0
signal-hook	0.3.17	0.4.4
json5	0.4.1	1.3.1
strum	0.26.3	0.28.0
serde	1.0.211	1.0.228
serde_json	1.0.132	1.0.150
libc	0.2.161	0.2.186
human-panic	2.0.2	2.0.8
futures	0.3.31	0.3.32
strip-ansi-escapes	0.2.0	0.2.1
tokio-util	0.7.12	0.7.18
tracing	0.1.40	0.1.44
tracing-error	0.2.0	0.2.1
tracing-subscriber	0.3.18	0.3.23
anyhow (build)	1.0.90	1.0.103
vergen-gix (build)	9.1.0	10.0.1

crossterm was inconsistent (hello-world already on 0.29.0, the rest on 0.28.1) — now harmonized to 0.29.0.

Code change

vergen-gix 10 renamed its builders (BuildBuilder/CargoBuilder/GixBuilder → Build/Cargo/Gix) and the all_*() constructors are now infallible. The component build script is updated accordingly — this is the only source change; everything else is a version bump.

Verification

cargo check --workspace --tests passes on all six generated projects (component, simple, simple-async, hello-world, event-driven, event-driven-async) against a freshly generated git repo, matching the CI flow.

Closes #91.

[orhun]

Hey, thanks for the PR!

The CI is failing due to vergen, can you check?

[yollu]

Thanks for the review, and good catch! The failure comes from the vergen-gix 9 → 10 bump in this PR. In v10, when the build runs outside a git repository (the CI generates the project without one), the VERGEN_GIT_* instructions are left unset instead of falling back to a default, which breaks env!("VERGEN_GIT_DESCRIBE") at compile time.

I've added Emitter::default_on_error() to the component build.rs, which restores the pre-v10 behaviour: real git values when a repo is present, and the idempotent placeholder when it isn't — so env!() always resolves. Verified locally with cargo check --tests on the generated component in a no-git directory (matching CI) — it now compiles cleanly.

Pushed (194b289). Could you re-run the workflow when you get a chance? Thanks!

[orhun]

thank you!