Feat tx builder v2 prototype

[Temasar1]

Thank you for contributing to Mesh! We appreciate your effort and dedication to improving this project. To ensure that your contribution is in line with the project's guidelines and can be reviewed efficiently, please fill out the template below.

Remember to follow our Contributing Guide before submitting your pull request.

Summary

#809
Basically this enforces a strict witness to mesh TxBuilder instead of the arbritriary tx buider order, this is a DSL like API call

instead of this which could be passed without other

tx.spendingPlutusScriptV3();
tx.txIn(txHash, index);
tx.txInScript(script);
tx.txInRedeemerValue(...);
tx.txOut(...);
tx.txOutInlineDatumValue(...);

we have this

tx.spendPlutusV3(txHash, index)
  .script(script)
  .redeemerJson(redeemer)
  .txOut(address, assets)
  .datumJson(datum);

Simple and easy to use without confusion

hii @twwu123 if you think this make sense and would be helpful lmk so i can proceed with other script purpose and looking how we can also chain others giving us a more cleaner interface.

also it is not conflicting the already Made MeshTxBuilder just a wrapper around what has been built

Please provide a brief, concise summary of the changes in your pull request. Explain the problem you are trying to solve and the solution you have implemented.

Affect components

Please indicate which part of the Mesh Repo

• [ ✅] @meshsdk/common
• @meshsdk/contract
• @meshsdk/core
• @meshsdk/core-csl
• @meshsdk/core-cst
• @meshsdk/hydra
• @meshsdk/provider
• @meshsdk/react
• @meshsdk/svelte
• [ ✅] @meshsdk/transaction
• @meshsdk/wallet
• Mesh playground (i.e. https://meshjs.dev/)
• Mesh CLI

Type of Change

Please mark the relevant option(s) for your pull request:

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Bug fix (non-breaking change which fixes an issue)
• Code refactoring (improving code quality without changing its behavior)
• Documentation update (adding or updating documentation related to the project)

Related Issues

Please add the related issue here if any

Checklist

Please ensure that your pull request meets the following criteria:

• My code is appropriately commented and includes relevant documentation, if necessary
• I have added tests to cover my changes, if necessary
• I have updated the documentation, if necessary
• All new and existing tests pass (i.e. npm run test)
• The build is pass (i.e. npm run build)

Additional Information

If you have any additional information or context to provide, such as screenshots, relevant issues, or other details, please include them here.