Apply protocol model pattern to missing types in Responses

[joseharriaga]

• Added a visitor to generate the protocol model pattern: 1) properties with setters, 2) public default constructor, 3) implicit conversion from BinaryContent for input models.
• Applied protocol model pattern to missing types in Responses, including the derived types of StreamingResponseUpdate, ResponseDeletionResult, and ResponseItemCollectionPage.
• Fixed an issue with CreateResponse methods overriding the value of StreamingEnabled. It is now the responsibility of the user to correctly set StreamingEnabled based on if they are calling the streaming or non-streaming method.
• Added validation that checks the value of StreamingEnabled based on which method it is being used with and throws an exception in case of invalid combinations.
• Changed the ConversationId property in CreateResponseOptions to match the ConversationOptions property of ResponseResult, i.e. type is now ResponseConversationOptions instead of just a string.
• Renamed MaxToolCalls in CreateResponseOptions to MaxToolCallCount to match the property in ResponseResult.
• Renamed Id in ResponseDeletionResult to ResponseId for clarity and consistency with other APIs in the library.
• fixes Modify ImplicitConversionToBinaryContentVisitor to allow for exception list #863