feat: add gap classification function to data quality toolbox

[karapeet95]

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which improves implementation)
• Performance (non-breaking change which improves performance. Please add associated performance test and results)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Non-functional change (xml comments/documentation/etc)

Contributor Checklist:

• My code follows the code style of this project.
• I have added an example of my new feature and included it in the documentation.
• 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.
• My Pull Request name follows the naming convention fix: <description>, feat: <description>, etc.

Reviewer Checklist for Charts compliant functions:

• The docstrings of the new function follow the contributing guidelines.
• The new function is professionally documented
• The new function and associated scripts are covered by one or more unit tests and code coverage did not decrease.
• The new function is accompanied by an example and it is included in the Gallery of Charts.
• The new function is reviewed in Chromatic. Access the storybook build results url and comment, approve or deny.
• All function inputs, arguments, and outputs have a supported data type and have human readable names.
• No code language is included in the description of the function or parameters (e.g use "polynomial order" instead of "poly_order")

[codecov]

Codecov Report

Attention: Patch coverage is 70.27027% with 11 lines in your changes missing coverage. Please review.

Project coverage is 90.81%. Comparing base (53651e0) to head (3da4c88).

Files with missing lines	Patch %	Lines
indsl/data_quality/gaps_classification.py	70.27%	10 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #395      +/-   ##
==========================================
- Coverage   91.00%   90.81%   -0.19%     
==========================================
  Files         110      111       +1     
  Lines        4178     4215      +37     
  Branches      550      556       +6     
==========================================
+ Hits         3802     3828      +26     
- Misses        232      242      +10     
- Partials      144      145       +1     

Files with missing lines	Coverage Δ
indsl/data_quality/gaps_classification.py	70.27% <70.27%> (ø)

[github-actions]

Unit Test Results

    18 files  ± 0      18 suites  ±0   32m 33s ⏱️ -41s
 1 189 tests + 7   1 189 ✅ + 7  0 💤 ±0  0 ❌ ±0 
15 345 runs  +63  15 337 ✅ +64  8 💤  - 1  0 ❌ ±0 

Results for commit 3da4c88. ± Comparison against base commit 53651e0.

♻️ This comment has been updated with latest results.

[neringaalt]

Feel free to adjust the year :)

[neringaalt]

This description is going to be visible for charts end-user if you are planning to expose this function. Thus, make sure it is clear and user friendly

[neringaalt]

You should split arguments into

arg: Name
   Description

e.g

Suggested change

	eps: The maximum distance between samples for clustering in DBSCAN. Defaults to 0.5.
	eps: The maximum distance between samples
	The maximum distance between samples for clustering in DBSCAN. Defaults to 0.5.

[neringaalt]

Add missing return type

[neringaalt]

Charts UI has support only for pd.Series. This also depends if you want to expose this function in Charts UI