fix: update to new lvt testing API

[adnaan]

Summary

Update all examples to use the new lvt testing API:

• StartDockerChrome now returns error instead of *exec.Cmd
• StopDockerChrome now takes (t, debugPort) instead of (t, cmd, debugPort)

This aligns with the latest lvt/testing package changes and fixes the cross-repo test failures.

Files Changed

• avatar-upload/avatar-upload_test.go
• counter/counter_test.go
• todos/todos_test.go

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR updates all example test files to use the new lvt testing API, which changes how Docker Chrome is started and stopped in E2E tests. The API now returns an error directly from StartDockerChrome instead of returning a command object, and StopDockerChrome no longer requires the command object as a parameter.

• Updated API usage to handle error returns from StartDockerChrome
• Modified cleanup calls to StopDockerChrome to use the new signature
• Applied consistent error handling pattern across all affected test files

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
todos/todos_test.go	Updated Chrome container lifecycle management to use new API with error handling
counter/counter_test.go	Updated Chrome container lifecycle management to use new API with error handling
avatar-upload/avatar-upload_test.go	Updated Chrome container lifecycle management to use new API with error handling

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[adnaan]

Closing - this fix is not needed as the examples repo CI needs to use the pinned lvt version. The cross-repo test in livetemplate is a separate issue.