Add unit tests for BeastType enum and conversions (u8, felt252)

[KevinMomanyi]

Pull Request Overview

📝 Summary

#Tasks

1. Write tests for:
   test_beast_type_to_u8(), test_u8_to_beast_type_valid(), test_u8_to_beast_type_invalid() and test_beast_type_to_felt252() using str_to_felt252()
2. Verify bidirectional mapping
   test_bidirectional_mapping()
3. Edge case testing
   test_u8_to_beast_type_invalid()

Related Issues

• Closes #(issue number) Replace with actual issue number.

Type of Change

Mark with an x all the checkboxes that apply (like [x]).

• 📝 Documentation (updates to README, docs, or comments)
• 🐛 Bug fix (non-breaking change which fixes an issue)
• 👌 Enhancement (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)

🔄 Changes Made

What's Changed

Provide a clear and concise description of what you changed and why.

Implementation Details

Describe how you implemented the changes.

Technical Notes

Include any technical details that reviewers should be aware of.

🔧 Tests Results

Describe the tests you performed to verify your changes.

Test Coverage

• [X ] Unit Tests
• Integration Tests
• Manual Testing

Evidence

Provide relevant evidence of testing (screenshots, test outputs, etc.).

Testing Notes

Include any special testing considerations or edge cases checked.

🔜 Next Steps

Indicate actions or improvements to be taken after this PR, if applicable.

[coxmars]

@KevinMomanyi add unit tests in the same file of the beast_type.cairo please

[coxmars]

Hi @KevinMomanyi please remove the scarb files from this PR, we only need the unit tests in the beast.cairo

[KevinMomanyi]

well noted @coxmars , thanks.

[coxmars]

@KevinMomanyi solve the issues in the workflow, the unit tests are not passing

Mistake in the review