Add a standardized batch minting workflow for faucets

[BrianSeong99]

Problem

Pioneer feedback reports that minting multiple notes from a faucet is not standardized.

The client exposes convenient single-mint flows, but higher-demand faucets need to mint many notes without building one-off custom scripts. Without a standard path, app teams implement their own batch minting logic and may create avoidable backlog or inconsistent behavior.

Why this matters

Batch minting is a natural faucet operation for apps that onboard many users, run campaigns, or need to distribute assets at higher throughput. If each team writes its own mint batching script, they also need to solve transaction construction, proving/submission, note tracking, and error handling themselves.

Proposed scope

Define and implement a standard faucet batch mint workflow in the client.

Potential API directions:

• a client helper that prepares multiple mint output notes from one faucet operation,
• integration with transaction batch support once BatchBuilder lands,
• guidance for proving/submitting many mint transactions safely,
• structured return values so callers can track each created note,
• documented limits and expected retry behavior.

If the desired client API requires a new Faucet MASM procedure, open a protocol follow-up after the client API shape is agreed.

Acceptance criteria

• There is a documented standard way to prepare/submit multiple mint notes from a faucet.
• The API or guide returns enough information to track each minted note.
• The workflow is aligned with BatchBuilder / transaction batch work.
• Known limits and failure modes are documented.
• Any required protocol/Faucet MASM follow-up is identified and linked.

Related context

• Introduce BatchBuilder #2085
• Batch building implementation #1821

[igamigo]

Some things to note here:

• This may not necessarily be related to BatchBuilder, as to build a batch you need to execute and prove a bunch of separate transactions and bundle them together
• Instead, maybe we want to have a single ProvenTransaction output a bunch of different notes. For this, we could modify TransactionRequestBuilder to allow for multiple targets when building a minting TransactionRequest
• The faucet already has sample code that emits a lot of notes in a single transaction. It might help guide pioneers as to how to do something similar in the meantime