Feature/unite project with team culture

[OlivieFranklova]

• add CODEOWNERS file
• add .pylintrc file
• add Black check to worflow
• format files with Black

Closes #18

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
1130	872	77%	70%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
column2Vec/impl/Column2Vec.py	98%	🟢
column2Vec/impl/functions.py	43%	🟢
similarity/Comparator.py	65%	🟢
similarity/ComparatorByColumn.py	81%	🟢
similarity/DataFrameMetadata.py	82%	🟢
similarity/DataFrameMetadataCreator.py	79%	🟢
similarity/Types.py	90%	🟢
similarity/functions.py	0%	🟢
TOTAL	67%	🟢

updated for commit: 3a0ab62 by action🐍

[miroslavpojer]

• pull
• code review
• test run - 80 passed, 2 skipped, 500 warnings

From the overall review, I have noted these points (as ideas only):

• Data and data_validation could be placed in the tests folder where they are used. Then, no repo structure explanation is needed in README.
• Why mention workflows? The README is for users. The developer will face it in the first PR.
• Did you think about a command line argument parser to avoid enabling inner features by editing main.py file?
• In README in How to run, I would expect sub-chapters describing how to reach variant: two variant of similarity and column2vec
• DataShow looks like three features. I saw only one line in README.
• I would add some duration value. Maybe an example of the output: 80 passed, 2 skipped, 500 warnings in 1887.83s (0:31:27)
• Consider a more detailed table of contents for users looking for exact parts.

[OlivieFranklova]

• pull
• code review
• test run - 80 passed, 2 skipped, 500 warnings

From the overall review, I have noted these points (as ideas only):

• Data and data_validation could be placed in the tests folder where they are used. Then, no repo structure explanation is needed in README.
• Why mention workflows? The README is for users. The developer will face it in the first PR.
• Did you think about a command line argument parser to avoid enabling inner features by editing main.py file?
• In README in How to run, I would expect sub-chapters describing how to reach variant: two variant of similarity and column2vec
• DataShow looks like three features. I saw only one line in README.
• I would add some duration value. Maybe an example of the output: 80 passed, 2 skipped, 500 warnings in 1887.83s (0:31:27)
• Consider a more detailed table of contents for users looking for exact parts.

• Data and data_validation could be moved in the future.
• Workflow note is removed from README.md
• Command line will be solved Add user interface #26
• How to run will be solved in Edit README.md #30
• DataShow will be solved in Edit README.md #30
• duration value added
• details table of contents will be solved in Edit README.md #30

[Zejnilovic]

In the end, this gets concatenated, why have it separate?

[OlivieFranklova]

Fixed

[miroslavpojer]

I saw

• 2 skipped tests
• 500 warnings

Are you planning to zero this indicators.

[OlivieFranklova]

I saw

• 2 skipped tests
• 500 warnings

Are you planning to zero this indicators.

I will resolve warnings in future
skipped tests will be resolved in #32