perf: optimize wasmer/cranelift in dev profile for faster tests

[sdbondi]

Summary

• Add [profile.dev.package.*] with opt-level = 2 for wasmer and cranelift crates across all 11 template Cargo.toml files
• Wasmer and Cranelift are ~10x slower when compiled in debug mode, making template tests painfully slow
• Optimizes only the JIT-heavy crates (wasmer, wasmer-compiler, wasmer-compiler-cranelift, cranelift-codegen, cranelift-frontend, cranelift-entity) without affecting the rest of the project

Test plan

• Run cargo test on individual templates to verify tests pass and are noticeably faster
• Verify templates render correctly with in_cargo_workspace == "false" (profile sections inside conditional blocks)
• Verify standalone templates (stable_coin, guessing_game) work correctly

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request optimizes the wasmer and cranelift crates in development and test builds across multiple Cargo.toml files to improve test performance. The reviewer suggested using glob patterns for package overrides to make the configuration more concise and maintainable.

[gemini-code-assist]

For better maintainability and conciseness, you can use glob patterns to specify the optimization level for multiple packages at once. Cargo's profile overrides support globs for package names, which can reduce the number of entries here from six to two.

This suggestion can be applied to all Cargo.toml files modified in this pull request.

Suggested change

	[profile.dev.package.wasmer]
	opt-level = 2
	[profile.dev.package.wasmer-compiler]
	opt-level = 2
	[profile.dev.package.wasmer-compiler-cranelift]
	opt-level = 2
	[profile.dev.package.cranelift-codegen]
	opt-level = 2
	[profile.dev.package.cranelift-frontend]
	opt-level = 2
	[profile.dev.package.cranelift-entity]
	opt-level = 2
	[profile.dev.package.'wasmer*']
	opt-level = 2
	[profile.dev.package.'cranelift-*']
	opt-level = 2