[feature]: automatically FinalizeBatch when running MintAsset by default

In order to simplify the on boarding of new users to the taproot assets protocol, we should automatically FinalizeBatch when running MintAsset by default (and have the option when running MintAsset to not automatically FinalizeBatch if we want to do it in two separate steps). New users likely just want to test minting an asset and will be confused of the purpose of the FinalizeBatch step. The FinalizeBatch step seems to be separate so that we can run MintAsset many times and then record all minted assets with a single on chain transaction. This is a very powerful function of the protocol, but it likely won't be used by new users, especially when they may only run MintAsset one or two times and on chain fees on main net may be low at the time, or they are running on testnet or regtest where there is no concern for fees.

Start by locating the MintAsset and FinalizeBatch entry points in the Go daemon and trace how the two operations currently interact. Done means MintAsset finalizes by default while exposing an option to keep finalization as a separate step, with the behavior verified for both paths.