feat(soil_type): Add SoilType class

[PabloVasconez]

Description

Please write a description of the changes you made here.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

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

• I have added tests that prove my fix is effective or that my feature works
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• New and existing unit tests pass locally with my changes

[github-actions]

Thank you so much for contributing to Blueprints! This is your Pull Request # 1 to this project.
Your contributions help thousands of engineers work more efficiently and accurately.

Now that you've created your pull request, please don't go away; take a look at the bottom of this page for the automated checks that should already be running. If they pass, great! If not, please click on 'Details' and see if you can fix the problem they've identified. A maintainer should be along shortly to review your pull request and help get it added!

[egarciamendez]

@PabloVasconez I think a SoilType must include some extra properties that could be expected in it. Let's put this PR as a draft for now until the next meeting.
@johan-tuls Any ideas?

[johan-tuls]

Soil properties do. For soil type we internally sticked to the general types that are also included here.
Only comment I might have, as they are all enums.
Is there no other option possible as enums are a finite list of options? That will be excluded now. But for what I can see it covers all I can think of