Add teams notification feature

[BharatKumarEY]

Integrating the notifications to Teams Channel

Description

I've expanded the notification capability within the spark_expectations library to include Microsoft Teams alongside the existing Slack notifications. This improvement allows users to receive updates on data quality job execution status across both Slack and Teams platforms.

Related Issue

Please link to the issue here: #56

Motivation and Context

The motivation behind this change is to broaden the reach of data quality framework execution status notifications. While Slack is a popular communication platform, some organizations prefer or exclusively use Microsoft Teams. By incorporating Teams notifications into the spark_expectation library, we enhance its usability for a wider audience, ensuring that data quality job execution status alerts are accessible across multiple collaboration tools.

How Has This Been Tested?

To ensure the reliability and functionality of the Teams notification feature, I thoroughly tested the following aspects:
Unit Tests:- Implemented unit tests to verify the correctness of the Teams notification implementation.
Integration Testing: Conducted integration tests by simulating different data quality scenarios and validating the generation and delivery of notifications to Teams.
Environment: Tested the feature in various environments like databricks, local IDEs as well as to ensure compatibility and functionality across different setups.
Message Formatting: Checked the appearance and readability of messages sent to Teams to ensure they display correctly.
Link to Unit test doccument:-
This comprehensive testing approach aimed to validate the feature's effectiveness, compatibility, and correctness before integrating it into the spark_expectations library.

Screenshots (if appropriate):

Test Results & Proofs - SE Teams Notif Feature.zip
Please refer the attachments section

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:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (6d546bb) 100.00% compared to head (171113c) 100.00%.

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #58   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines         1441      1441           
=========================================
  Hits          1441      1441           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.