⚡ Optimize string concatenation in OptionCollector

[Dor-bl]

💡 What: Replaced inefficient string concatenation in ParseCapabilitiesIfWindows within OptionCollector.cs with a List<string> and string.Join(). Initialized the list with the exact required capacity.
🎯 Why: The existing approach (result = result + ", " + key + ": " + value) inside a loop leads to repeated string memory allocations, causing higher CPU usage and Garbage Collection pressure. The list accumulation approach is the standard C# optimization.
📊 Measured Improvement: Created a local benchmark executing the loop 100,000 times on a simulated 50-item capability dictionary:

• Baseline (String Concatenation): ~2762 ms
• Optimized (List Add + String.Join): ~1029 ms
• Overall Improvement: ~62% execution time reduction.

---

PR created automatically by Jules for task 17089181951364035381 started by @Dor-bl

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[Copilot]

Pull request overview

This PR optimizes how Windows default-capabilities arguments are serialized in OptionCollector to reduce allocations during repeated string concatenation, and adds a small benchmark project to compare approaches.

Changes:

• Refactored ParseCapabilitiesIfWindows to accumulate capability fragments in a List<string> and emit the final string via string.Join.
• Added a standalone benchmark console app to measure old vs new concatenation approaches.
• Introduced a new benchmark project file to build/run the benchmark.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/Appium.Net/Appium/Service/Options/OptionCollector.cs	Replaces loop-time string concatenation with list accumulation + string.Join for Windows capability argument formatting.
benchmark/Program.cs	Adds a simple stopwatch-based benchmark comparing old and new concatenation strategies.
benchmark/benchmark.csproj	Defines the benchmark console project and its target framework.

---

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

[Copilot]

The benchmark project targets net10.0, but this repo’s CI/tooling is configured for older SDKs (unit-test workflow installs .NET 8.0.x, release workflow installs .NET 5.0.x). Even though the benchmark isn’t in Appium.Net.sln today, keeping it on a newer TFM can make it difficult for contributors to build/run without extra SDK installs. Consider targeting net8.0 (or otherwise aligning the benchmark TFM with the repo’s supported SDK range).

Suggested change

	<TargetFramework>net10.0</TargetFramework>
	<TargetFramework>net8.0</TargetFramework>