Use generated JSON context for event args

[RenderMichael]

User description

Thanks for contributing to Selenium!
A PR well described will help maintainers to quickly review and merge it

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, help reviewers by making them as simple and short as possible.

Motivation and Context

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

---

PR Type

Enhancement

---

Description

• Replaced static JSON options with generated JSON context.

• Updated domain generator to include protocol version.

• Adjusted event argument deserialization to use generated JSON context.

---

Changes walkthrough 📝

Relevant files

Enhancement

DevToolsJsonOptions.cs Removed static JSON options class.                                              dotnet/src/webdriver/DevTools/Json/DevToolsJsonOptions.cs Removed the DevToolsJsonOptions class. Eliminated static JsonSerializerOptions configuration. +0/-35    DomainGenerator.cs Added protocol version to domain generator.                            third_party/dotnet/devtools/src/generator/CodeGen/DomainGenerator.cs Added protocol version extraction from root namespace. Passed protocol version to domain generator context. +3/-1      domain.hbs Updated event deserialization to use generated JSON context. third_party/dotnet/devtools/src/generator/Templates/domain.hbs Replaced static JSON options with generated JSON context. Updated event argument deserialization logic. +1/-1

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Error Handling The event deserialization code lacks error handling for cases where deserialization fails. Consider adding try-catch block to handle potential JSON deserialization exceptions. var eventArgs = e.EventData.Deserialize(eventData.EventArgsType, {{rootNamespace}}.{{protocolVersion}}JsonSerializerContext.Default);

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Add null check for data safety Add null check before deserializing event data to prevent potential NullReferenceException if EventData is null third_party/dotnet/devtools/src/generator/Templates/domain.hbs [63] -var eventArgs = e.EventData.Deserialize(eventData.EventArgsType, {{rootNamespace}}.{{protocolVersion}}JsonSerializerContext.Default); +var eventArgs = e.EventData?.Deserialize(eventData.EventArgsType, {{rootNamespace}}.{{protocolVersion}}JsonSerializerContext.Default); Apply this suggestion Suggestion importance[1-10]: 8 Why: Adding a null check using the null-conditional operator (?.) is a crucial defensive programming practice that prevents potential NullReferenceException when EventData is null, making the code more robust and reliable.	8