Generic TSS

[gouthamp-stellar]

What

Making TSS generic - work for all transactions. Implementation of the doc: https://docs.google.com/document/d/1MJ3iyiTbASJp8hq1cTJO_aHDtP3Ko7kpMnKqzjYhITE/edit?tab=t.0

Why

We need to make TSS work for all types of transactions and not just the disbursement use case

Known limitations

N/A

Issue that this PR addresses

#79

Checklist

PR Structure

• It is not possible to break this PR down into smaller PRs.
• This PR does not mix refactoring changes with feature changes.
• This PR's title starts with name of package that is most changed in the PR, or all if the changes are broad or impact many packages.

Thoroughness

• This PR adds tests for the new functionality or fixes.
• All updated queries have been tested (refer to this check if the data set returned by the updated query is expected to be same as the original one).

Release

• This is not a breaking change.
• This is ready to be tested in development.
• The new functionality is gated with a feature flag if this is not ready for production.

[aristidesstaffieri]

Should this work for transactions that need a specific signer(s)?
If so maybe we could use an option to submit an already signed tx and only build it instead of build + sign it?