refactor: remove redundant type from object creation expressions #360
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This PR refactors multiple object instantiation sites to leverage C# target-typed
newexpressions, removing redundant type names from the right-hand side when the type is already declared on the left. All occurrences ofnew Type(...)ornew Type()have been updated tonew(...)ornew()respectively, improving code readability and reducing verbosity.newexpressions (new(...)ornew()), streamlining the code and adhering to modern C# best practices.