Chore/folder structure

[Yagth]

Description

This PR contains a different folder structure.

1. All the reduct related codes except for utility functions are moved into a separate reduct folder.
2. Inside the reduct folder, the previous enf-reducer is renamed to boolean-reduct without changing it's content.
3. All codes that belong to previous implementations are removed from the code base. This makes our code base simple and more organized. The details of removed files may be hard to list down here but the previous boolean-reduct and enf-checkers are removed. If anyone would like to reference these codes, they can now be found in the v0.2.0 tag.
4. The files that are removed are mainly relating to list and tree datastructures, which we aren't using anymore.

Motivation and Context

• This PR is aimed to reduce the clutter in our code base and make it more readable. Codes and functions that doesn't work and aren't actively maintained will not add any value to the reader except confusion.
• Removed codes' purpose was mainly to be used as a reference which can be done via the use of git tags.
• The new folder structure can help us scale and organize our code better as we move forward with the implementation of moses, not just reduct.

How Has This Been Tested?

I have tested it locally using our python script to make sure all the active test cases pass.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [x] Breaking change (folder structure that would affect existing code organization)

Checklist:

• [x] My code follows the code style of this project.
• [x] All new and existing tests passed.
• [ ] I have added tests to cover my changes. This part isn't applicable since I only changed the folder structure

[Yagth]

@iCog-Labs-Dev/moses I recommend you guys take a look the changes introduced in this PR. Note that the repository is also renamed to metta-moses instead of metta-moses-reduction.