Add base16 and base32 encoding example files

[mathurojus]

This PR adds new examples using base16 and base32 encodings in the examples folder as requested in issue #391 and by @vil02. Includes both standard and output-size reduction variants.

Closes #391

[vil02]

@mathurojus: thanks for creating this PR!

Please run_all_examples.sh to see why the CI will fail. Let me know if you need some support.

Regarding the example files: I am not sure if they are needed. I think that just mentioning in the existing example, that one can use "base16" and "base32" for the encoding should be enough.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (727cd47) to head (0755943).

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #393   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           17        17           
  Lines          336       336           
  Branches        26        26           
=========================================
  Hits           336       336           

☔ 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.

[mathurojus]

Hi @vil02,

I've addressed all your review comments:

✅ Deleted the 3 new example files (base16_example.py, base16_to_reduce_output_size.py, base32_to_reduce_output_size.py) as you suggested - instead of adding new files, I updated the existing examples.

✅ Updated base85_to_reduce_output_size.py to mention that base16 and base32 encoding can also be used, with a note clarifying that they increase (not reduce) output size.

✅ Resolved all 4 conversation threads related to the incorrect import statements and misleading comments about output size.

The changes should fix the CI issues. The import statement in the original files is already correct (from puzzle_generator.create_puzzle import create), and the misleading comments have been corrected.

Ready for you to approve the workflows and re-review. 🚀

[vil02]

@mathurojus: there is a fundamental problem with this change. Will the code like:

create(_PUZZLE, encoding="base32")

work?

No, because this package does not implement the base32 encoding.

You need to add the files like:

• bytestr_utils_64.py,
• bytestr_utils_85.py,

and modify bu_configurators.py accordingly.

Please remember about updating the related tests.