feat: added cryptoTransfer to CryptoAllowance to showcase support in HIP906

[quiet-node]

Description:

• renamed IHRC contracts to IHRC719 as IHRC632 is being included
• included IHRC632. IHRC632 allows an EOA to act as an SC with IHRC632 interface, walletAIHrc632 = new Contract(walletA.address, IHRC632, walletA);. This will make it possible for the EOA to directly make calls to the HAS precompile contracts, hence making the EOA top level caller of the transaction without any help from a third party like another SC account. That's when Hip-906 kicks in and allow hbar owner, top level caller, grant an hbar allowance to a spender.
• added cyprtoTransfer to CryptoAllowance to showcase support in HIP906

Related issue(s):

Fixes #797

Notes for reviewer:

Checklist

• [x] Documented (Code comments, README, etc.)
• [x] Tested (unit, integration, etc.)

[github-actions[bot]]

Test Results

  17 files  +  3    86 suites  +16   7m 54s :stopwatch: + 1m 18s 254 tests +19  246 :heavy_check_mark: +17    7 :zzz: +1  1 :x: +1  286 runs  +51  275 :heavy_check_mark: +46  10 :zzz: +4  1 :x: +1 

For more details on these failures, see this check.

Results for commit 18f09007. ± Comparison against base commit 024064d7.

:recycle: This comment has been updated with latest results.

[quiet-node]

overall looks good, leaved some nits and comments.

Also, I would like to see the test cases defined as:

1. Grant Allowance (approve) from EOA to EOA
2. Grant Allowance (approve) from EOA to Contract
3. Grant Allowance (approve) from Contract to EOA
4. Grant Allowance (approve) from Contract to Contract
5. Get Current Allowance from owner account to another Account
6. Get Current Allowance from owner account to an Smart Contract

I also think that the correct resolution of these scenarios will need for the EOA to call the system contract directly. due to Security model limitations.

Finally, not sure why are we adding this examples and tests as part of the HTS-Precompile folder, since is not related to HTS transfers but I would place it in its own folder called HAS-SystemContract (Hedera Account Service System Contract)

@AlfredoG87

1. Grant Allowance (approve) from EOA to EOA

   • EOA -> EOA via HAS
   • EOA -> EOA via IHRC632

2. Grant Allowance (approve) from EOA to Contract

   • EOA -> SC via IHRC632

3. Grant Allowance (approve) from Contract to EOA

   • SC -> EOA via HAS

4. Grant Allowance (approve) from Contract to Contract

   • contract -> contract via IHRC632 + IHAS

5. Get Current Allowance from owner account to another Account

   • allowance from an SC to EOA

6. Get Current Allowance from owner account to an Smart Contract

   • allowance from EOA to another account