Add HIP-423: Long Term Scheduled Transactions

[agadzhalov]

Description

Implement support for the changes introduced by HIP-423 in the SDK, enabling developers to create and manage Long Term Scheduled Transactions with enhanced functionality. This involves adding new fields and handling updated response codes for scheduled transactions, as well as providing a clear API design that SDKs should follow.

Acceptance Criteria

1. Make sure fields implemented and that they are built into the transaction protobuf upon execution.

• expirationTime
• waitForExpiry

2. Handle New Status Codes:

• SCHEDULE_EXPIRY_MUST_BE_IN_FUTURE
• SCHEDULE_EXPIRY_TOO_LONG
• SCHEDULE_EXPIRY_IS_BUSY

3. Update ScheduleExample. The example will look like

1. Create an account with a keylist of two keys and an initial balance of 2 Hbar.
2. Schedule a transfer transaction of 1 Hbar from the created account to the operator account with an `expirationTime` of 24 hours in the future and `waitForExpiry=false` .
3. Sign the transaction with one key.
4. Verify that the transfer does not execute.
5. Sign the transaction with the other key.
6. Verify the transfer executes successfully.
7. Schedule another transfer transaction of 1 Hbar from the account to the operator account with an `expirationTime` of 30 seconds in the future and `waitForExpiry=true` .
8. Sign the transaction with one key.
9. Verify that the transfer does not execute.
10. Update the account’s key to be only the one key that has already signed the scheduled transfer.
11. Verify that the transfer successfully executes roughly at the time of its expiration.

4. Testing: Implement tests