Fix/read version

[dreaquil]

Description

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

• Fixes version is hard-coded in setup.py. This should be read from either VERSION.txt file or in anomalib.__init__.py #36 (issue)

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 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

[samet-akcay]

@dreaquil, thank you for creating the PR. There is currently a problem with our CI. Once fixed, we'll test this.

[dreaquil]

Resolved 0.2.5 merge conflict.

[samet-akcay]

@dreaquil CI fails when VERSION is used, which was the reason why the version was hardcoded as a temporary fix. I'll look into it. I've attached the log file here.

CI.log

[samet-akcay]

PR #229 addressed the issue. We had to modify get_version function. We could close this PR. Thanks for the efforts!