Fix mypy pep561

[WenjingKangIntel]

Description

• Provide a summary of the modification as well as the issue that has been resolved. List any dependencies that this modification necessitates.

With this PR, when running
python setup.py install, python setup.py install sdist or python setup.py sdist bdist_wheel, py.typed will be included in the build package.

• Fixes [Task]: Make anomalib PEP 561 compliant for mypy #1015

Changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which refactors the code base)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist

• My code follows the pre-commit style and check guidelines of this project.
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing tests pass locally with my changes
• I have added a summary of my changes to the CHANGELOG (not for minor changes, docs and tests).

[WenjingKangIntel]

@ashwinvaidya17 Could you please help double check this? Thanks!

[ashwinvaidya17]

Do we really need sdist and bdist_wheel in the package?

[WenjingKangIntel]

Do we really need sdist and bdist_wheel in the package?

Without this pr, even pure python setup.py install will not include py.typed in the package. FYI.

[WenjingKangIntel]

From this link:
https://setuptools.pypa.io/en/latest/userguide/datafiles.html#summary
include_package_data
Accept all data files and directories matched by MANIFEST.in or added by a plugin.

include_package_data needs to explicitly set to True because we are using MANIFEST.in to match files.

[ashwinvaidya17]

From what I tested
package_data={"": ["config.yaml"], "anomalib": ["py.typed"]},
should be sufficient

[WenjingKangIntel]

Yes, I've tested it as well. It worked. But if we are going to use MANIFEST.in, we need to use the include_package_data=True.
If we are going to use package_data={"": ["config.yaml"], "anomalib": ["py.typed"]},, then we need to remove py.typed from MANIFEST.in, because they have duplicated functionality, which is to include the same file.

To sum up, if we do not use include_package_data=True, MANIFEST.in will not take effect.