Fix test checking return value of void function

[Copilot]

Test case incorrectly captured and asserted the return value of execute(), which has a void return type.

Changes

• Modified test case 15 to verify execute() doesn't throw instead of testing its return value
• Aligned with pattern used by other test cases in the file

// Before
const result = execute(textField, event);
expect(result).toBeUndefined();

// After
expect(() => {
    execute(textField, event);
}).not.toThrow();

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull Request Overview

This PR improves test coverage and corrects package-lock.json configuration by refining a test case assertion and removing unnecessary "peer": true flags from dependency entries.

• Updated test case 15 to verify the function doesn't throw instead of checking for undefined return
• Removed incorrect "peer": true flags from package-lock.json entries

Reviewed Changes

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

File	Description
packages/text/src/TextField/usecase/TextFieldKeyDownEventUseCase.test.ts	Updated test case 15 to use .not.toThrow() assertion instead of checking for undefined return value, better aligning with the function's void return type
package-lock.json	Removed "peer": true flags from various dependency entries to correct package configuration

---

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