Implement bundle burn validation and serialization

[dmidem]

This pull request introduces handling of the 'burn' field of the bundle. The changes are split across two new modules: burn_validation and burn_serialization.

Burn Validation
The burn_validation module ensures the correctness of burn operations. Specifically, it validates that each asset to be burned is unique, non-native, and has a non-zero amount.

Burn Serialization
The burn_serialization module is responsible for reading and writing assets and burns from/to a stream.

[what-the-diff]

PR Summary

• Added a new module for serialization
  A new module burn_serialization has been added to the orchard component.
• Introduced functions for reading/writing bundle burn data
  A new function read_bundle_burn() is added for reading, while modifications have been made to existing functions for writing bundle burns.
• Updated the serialization of version 5 transactions (Sapling)
  The existing function write_v5_bundle() has been modified to support writing bundle burn data into bytes.
• Created a module for burn validation
  A new module called 'burn-validation' is added with a method that validates whether all assets being burned have unique identifiers, non-zero amounts and aren't native assets themselves. It returns an error or success based on the validation results.

[dmidem]

Closing this in favor of PR #38