Fix TokenInfoHTSSuite tests

[MiroslavGatsanoga]

Description:

Fix child record issues related to token info precompile, making TokenInfoHTSSuite passing as a result.

Also enable a couple of tests in DefaultTokenStatusSuite since changes to read-only precompiles are related to them.

Related issue(s):

#9427

Notes for reviewer:

Checklist

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

[github-actions]

Node: HAPI Test Results

1 242 tests   783 ✔️  1h 21m 33s ⏱️
   165 suites  459 💤
   165 files        0 ❌

Results for commit 04a9c7f.

♻️ This comment has been updated with latest results.

[github-actions]

Node: E2E Test Results

    1 files      1 suites   20m 56s ⏱️
310 tests 310 ✔️ 0 💤 0 ❌
332 runs  332 ✔️ 0 💤 0 ❌

Results for commit 04a9c7f.

♻️ This comment has been updated with latest results.

[github-actions]

Node: Unit Test Results

    2 263 files      2 263 suites   1h 24m 28s ⏱️
118 261 tests 118 227 ✔️ 34 💤 0 ❌
126 520 runs  126 486 ✔️ 34 💤 0 ❌

Results for commit 04a9c7f.

♻️ This comment has been updated with latest results.

[codecov]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (43c6178) 65.26% compared to head (04a9c7f) 65.29%.
Report is 1 commits behind head on develop.

Additional details and impacted files

@@              Coverage Diff              @@
##             develop    #9509      +/-   ##
=============================================
+ Coverage      65.26%   65.29%   +0.02%     
- Complexity     29678    29685       +7     
=============================================
  Files           3262     3260       -2     
  Lines         124581   124575       -6     
  Branches       12918    12919       +1     
=============================================
+ Hits           81310    81342      +32     
+ Misses         40194    40157      -37     
+ Partials        3077     3076       -1     

Files	Coverage Δ
...mpl/exec/scope/HandleSystemContractOperations.java	100.00% <100.00%> (ø)
...impl/exec/scope/QuerySystemContractOperations.java	100.00% <ø> (ø)
...tracts/hts/AbstractNonRevertibleTokenViewCall.java	100.00% <100.00%> (ø)
...s/hts/fungibletokeninfo/FungibleTokenInfoCall.java	93.75% <100.00%> (ø)
...c/systemcontracts/hts/tokeninfo/TokenInfoCall.java	93.33% <100.00%> (ø)
...emcontracts/hts/nfttokeninfo/NftTokenInfoCall.java	91.30% <85.71%> (-4.16%)	⬇️

... and 12 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

Node: Integration Test Results

280 tests   280 ✔️  32m 27s ⏱️
    5 suites      0 💤
    5 files        0 ❌

Results for commit 04a9c7f.

♻️ This comment has been updated with latest results.

[tinker-michaelj]

Looks great @MiroslavGatsanoga, very cool to see these tests passing. 🙌

I don't think we actually need to pass in the MessageFrame to these HtsCall implementations, however.

1. The ProxyWorldUpdater's method to externalize system contract result just directly calls an Enhancement method; and the HtsCall implementations already have access to the Enhancement.
2. For mono-service compatibility, we don't want to skip externalizing the result for any static frame, but only if we are in a ContractCallLocalQuery instead of a HAPI transaction; compare here in mono-service.

I think we just need to make the QuerySystemContractOperations method here a no-op; and then remove the MessageFrame injections. 🤔

[MiroslavGatsanoga]

Looks great @MiroslavGatsanoga, very cool to see these tests passing. 🙌

I don't think we actually need to pass in the MessageFrame to these HtsCall implementations, however.

1. The ProxyWorldUpdater's method to externalize system contract result just directly calls an Enhancement method; and the HtsCall implementations already have access to the Enhancement.
2. For mono-service compatibility, we don't want to skip externalizing the result for any static frame, but only if we are in a ContractCallLocalQuery instead of a HAPI transaction; compare here in mono-service.

I think we just need to make the QuerySystemContractOperations method here a no-op; and then remove the MessageFrame injections. 🤔

1. Ah, missed that I can use Enhancement directly instead of ProxyWorldUpdater, will update it with that and remove the injected MessageFrames.
2. I think I see why this will work, just want to check my understanding: Making QuerySystemContractOperations method a no-op (which basically means to skip it) instead of checking something like proxyUpdater.isInTransaction() as in mono will work because of the @QueryScope annotation which is meant for the ContractCallLocalQuery case. Right?

Will push the updates shortly, tyvm @tinker-michaelj!

[tinker-michaelj]

LGTM, ty @MiroslavGatsanoga