feat: add automation_status field to test case creation

[cbowerQ2]

🔧 Add automation_status field to test case creation

📋 Summary

This PR adds support for the automation_status field when creating test cases via the BrowserStack Test Management API. This field allows users to specify the automation status of test cases (e.g., not_automated, automated, automation_not_required) directly during creation.

🎯 Motivation

The automation_status field is already supported by the BrowserStack Test Management API and is returned in API responses, but was not exposed in the MCP server's test case creation functionality. This created a gap where users couldn't set this important QA workflow field during test case creation.

🔍 What Changed

• Added automation_status?: string to TestCaseCreateRequest interface
• Added optional automation_status field to the Zod schema with validation and documentation
• Updated sanitizeArgs() function to handle null values for the new field
• Added test coverage for the new field

✅ Backward Compatibility

• Fully backward compatible - the field is optional
• Existing code continues to work unchanged
• No breaking changes to the API surface

🧪 Testing

• ✅ All existing tests pass
• ✅ Added test case with automation_status field
• ✅ Schema validation works correctly
• ✅ Handles optional/null values properly

📚 API Reference

This aligns with the official BrowserStack API documentation:

• Create Test Case API
• Common values: not_automated, automated, automation_not_required

🎉 Impact

Users can now fully manage test case automation status through the MCP server, enabling complete QA workflow automation without manual steps in the BrowserStack UI.

Files Changed: 2 files, 9 insertions

• src/tools/testmanagement-utils/create-testcase.ts - Core implementation
• tests/tools/testmanagement.test.ts - Test coverage

[ruturaj-browserstack]

Thanks for the PR, @cbowerQ2 🎉
@Vishalan please go ahead and merge — I’ve tested it and everything works as expected. ✅