Validate field type on serializing

[cffls]

Validate each field in CBORSerializable during serialization. This will avoid bugs caused by incorrect type of field. For instance, when a field should be Address type, but being a string type instead, it would've been serialized successfully but failed to be deserialized.

This validation also helped discovering two minor type mismatch in unit tests. 🥳

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 87.09677% with 4 lines in your changes missing coverage. Please review.

Project coverage is 85.60%. Comparing base (95881a0) to head (b3bccb6).
Report is 206 commits behind head on main.

Files with missing lines	Patch %	Lines
pycardano/serialization.py	86.66%	1 Missing and 3 partials ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #208   +/-   ##
=======================================
  Coverage   85.59%   85.60%           
=======================================
  Files          26       26           
  Lines        2853     2882   +29     
  Branches      677      693   +16     
=======================================
+ Hits         2442     2467   +25     
- Misses        304      305    +1     
- Partials      107      110    +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[nielstron]

Very neat! I like how this also applies to everything that is serialized very elegantly.

[nielstron]

I just tried this with the error I initially reported. Its a better error message for sure, but there is still some improvement possible :)

    builder.required_signers = ["string!"]

results in

TypeError: Field 'required_signers' should be of type typing.Union[typing.List[pycardano.hash.VerificationKeyHash], 
NoneType], got <class 'list'> instead.

The error here is that I have a list of "str" and not list of the required type, which upsets the type checker - it fails to point out the precise violation though.

I think the only reasonable fix for this would be a recursive type printer. Will look into that.

[nielstron]

Suggestion: Instead of printing the type of the violating object (which may hide recursive errors), just print the violating value? This also helps the developer debug, as they might have a better grip on where a value comes from than what type it has.

Changes the error message to

TypeError: Field 'required_signers' should be of type typing.Union[typing.List[pycardano.hash.VerificationKeyHash], 
NoneType], got ['string!'] instead.