feat: add miden::standards::note_tag module

[PhilippGackstatter]

Follow-up to #2329 that removes miden::protocol::note::build_note_tag_for_network_account and adds miden::standards::note_tag.

It contains two procedures:

• create_account_target - equivalent to NoteTag::with_account_target
• create_custom_account_target - equivalent to NoteTag::with_custom_account_target

Setting note tags for notes targeted at network accounts may no longer be useful, as mentioned here. So, the current use of this procedure in create_burn_note may not be necessary. The logic still seems useful to have when creating notes targeted at local accounts at runtime.

Includes various small doc fixes and replaces magic numbers with constants.

Replaces ExecutionError with ExecError in CodeExecutor for better out-of-the-box error messages in failing tests.

[partylikeits1983]

In what scenario would it be required to create a NoteTag with a tag length greater than 1? Does this mean that the note can have multiple tags?

[PhilippGackstatter]

I'm not quite sure I understand the question. A note tag with len 0 or 1 would contain 0 or 1 bit from the account ID prefix, so it'd be almost useless. So for useful note tags we almost always want a tag with len greater than 1. (Default is 14).

I think the reason to support 0 is mainly for API uniformity, so you can pass any value in 0..=32, but also so you can easily "nullify" a note tag by passing len = 0, if you don't want a tag.

Not sure if this answers the question.

[partylikeits1983]

Looks good! Thanks for updating the bridge out masm code :)

[bobbinth]

Looks good! Thank you! I left one comment inline - but it is not directly related to this PR.

[bobbinth]

Not directly related to this PR, but why do we need to set a tag for a BURN note? These are network notes and instead of a tag we should be setting an attachment for them, no?

[bobbinth]

I'll merge this PR as is - but cc @partylikeits1983 and @mmagician in case this is something we'd want to update in a different PR.