🎉 Add Azure Content Moderator service for image analysis

[teresaqhoang]

Motivation and Context

This pull request adds content moderation and image handling features to the project. Specifically, it adds a new ContentModeratorController with endpoints for detecting sensitive image content and getting the status of content moderation. It also adds image text validation to the DocumentImportController, throwing an exception if an image does not contain text.

Additionally, this pull request adds an AzureContentModerator service and a ContentModeratorOptions class for configuring content moderation. The Azure Content Moderator service allows for the analysis of images to detect harmful content, such as hate speech, sexual content, self-harm, and violence.

The pull request also includes updates to the ChatInput and DocumentsTab components in the webapp to support the new features, including the use of the new useContentModerator hook for content moderation and the useFile hook for image upload handling.

Description

webapp

• Add image moderation and import handling to useFile hook: Add loadImage and handleImport functions to useFile hook.
  • loadImage function loads an image from a URL and returns a promise.
  • handleImport function handles importing a file and returns a promise.
• Add ContentModerationService for image moderation.
  • analyzeImageAsync method analyzes an image for content moderation.
  • getContentModerationStatusAsync method checks the status of the content moderation service.

webapi

• The ChatSkill now includes an instance of AzureContentModerator which can be used to moderate user input when an image is uploaded.
• The appsettings.json file has been updated to include configuration options for the service.
• The ChatInput component has been updated to include a new hook useContentModerator which handles document import, including using the Azure Content Moderator API to analyze image content for offensive or unwanted elements. - The handleImport function in ChatInput has been removed and replaced with a shared function in useFile that handles file imports. Also refactored document import in DocumentsTab component to use useFile hook.

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the Contribution Guidelines and the pre-submission formatting script raises no violations
  - [ ] All unit tests pass, and I have added new tests where possible
• I didn't break anyone 😄

[crickman]

DocumentImportController is within a week or two of being deleted and all of this work will need to be ported to the semantic-memory service. I wonder if just landing this in semantic-memory as a first step doesn't make more sense?

[teresaqhoang]

DocumentImportController is within a week or two of being deleted and all of this work will need to be ported to the semantic-memory service. I wonder if just landing this in semantic-memory as a first step doesn't make more sense?

As part of the semantic-memory work, nearly all of the image processing logic is being moved to semantic-memory, in the relatively near-term. I wonder if it makes sense to coordinate this feature within that scope?

Definitely makes sense to coordinate this feature within the semantic-memory work. Pausing this PR until then.