refactor: drop explicit types on new expressions #361
                
     Merged
            
            
          
  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 object instantiations to leverage C# target-typed new expressions, removing redundant type names on the RHS when the type is already declared on the LHS.
new TypeName(...)syntax even though the variable type was obvious from the left-hand side. All such occurrences—ranging from dictionaries and resolvers to domain events, factories, mocks, repositories, and unit-test setups—have been updated to the concisenew(...)form. This reduces boilerplate, improves readability, and aligns the code with modern C# best practices.