add ci cd test

# Conflicts:
#	consensus/src/processes/transaction_validator/transaction_validator_populated.rs
#	crypto/txscript/Cargo.toml

- Add threshold_scenario_limited_one_time function
- Add threshold_scenario_limited_2_times function
- Create generate_limited_time_script for reusable script generation
- Implement nested script structure for two-times borrowing
- Update documentation for both scenarios
- Add tests for owner spending, borrowing, and invalid attempts in both cases
- Ensure consistent error handling and logging across scenarios
- Refactor to use more generic script generation approach

# Conflicts:
#	consensus/src/processes/transaction_validator/transaction_validator_populated.rs
#	crypto/txscript/src/lib.rs
#	crypto/txscript/src/opcodes/mod.rs
#	crypto/txscript/src/standard/multisig.rs
#	wallet/pskt/src/pskt.rs

run tests against both kip1- enabled/disabled engine

add tests covering new opcodes

add comments describing why 2 files are used.

* Use ForkActivation for all fork activations

* Avoid using negation in some ifs

* Add is_within_range_from_activation

* Move 'is always' check inside is_within_range_from_activation

* lints

* Cleanup manual block level calc

There were two areas in pruning proof mod that
manually calculated block level.

This replaces those with a call to calc_block_level

* Refactor pruning proof build functions

* Refactor apply pruning proof functions

* Refactor validate pruning functions

* Add comments for clarity

reorder kip10 opcodes.
reflect script tests

# Conflicts:
#	consensus/core/src/config/params.rs
#	consensus/src/consensus/services.rs
#	consensus/src/processes/transaction_validator/mod.rs
#	testing/integration/src/consensus_integration_tests.rs

Change TxScriptEngine::from_transaction_input to assert valid input index
instead of returning Result. This better reflects that an invalid index is a
caller's (transaction validation) error rather than a script engine error,
since the input must be part of the transaction being validated.

An invalid index signifies a mismatch between the transaction and the input being
validated - this is a programming error in the transaction validator layer, not
a script engine concern. The script engine should be able to assume it receives
valid inputs from its caller.

The change simplifies error handling by enforcing this invariant early,
while maintaining identical behavior for valid inputs. The function is
now documented to panic on malformed inputs.

This is a breaking change for code that previously handled
InvalidIndex errors, though such handling was likely incorrect
as it indicated an inconsistency in transaction validation.

refactor vector filling

Co-authored-by: Michael Sutton <[email protected]>

block that contains the tx with kip10 opcode is accepted after daa score has being reached

Fallible conversion of output amount (usize -> i64)

Co-authored-by: Michael Sutton <[email protected]>

Fallible conversion of input amount (usize -> i64)

Co-authored-by: Michael Sutton <[email protected]>

9 byte integers must fail to serialize

Co-authored-by: Michael Sutton <[email protected]>

Co-authored-by: Michael Sutton <[email protected]>

Co-authored-by: Michael Sutton <[email protected]>