test: add maxAutomaticTokenAssociations tests

[ivaylonikolov7]

Description:

Adds integration tests for maxAutomaticTokenAssociations according to HIP-904 test plan.

This PR modifies TokenAssociateIntegrationTest.js by adding additional tests according to this test plan:

LIMITED AUTO ASSOCIATIONS [0-5000] (some sdks don’t have tests for these flows)

1. Given 2 fungible tokens, a sender account with a balance of the 2 fungible tokens, and a receiver account with 1 auto associations, when token1 is transferred from the sender to the receiver account, then the receiver account contains the sent balance of the token and when token2 is transferred from the sender to the receiver account, then the transaction fails with NO_REMAINING_AUTOMATIC_ASSOCIATIONS
2. Same test as above but with NFTs
3. Given a fungible token, a sender account with a balance of the fungible token, a receiver account with no auto associations, and the fungible token is manually associated with the receiver account, when the token is transferred from the sender to the receiver account, then the receiver account contains the sent balance of the token
4. Given an NFT, a sender account with 1 minted NFT, a receiver account with no auto associations, and the NFT is manually associated with the receiver account, when the NFT is transferred from the sender to the receiver account, then the receiver account contains the NFT (this is same as above but with NFT)

UNLIMITED AUTO ASSOCIATIONS -1

1. Given 2 fungible tokens, a sender account with a balance of the 2 fungible tokens, and a receiver account with 1 auto associations, when token1 is transferred from the sender to the receiver account, then the receiver account contains the sent balance of the token and when token2 is transferred from the sender to the receiver account, then receiver account contains the sent balance of the token
2. Same test as above but with NFTs
3. Given a fungible token, a holder account with a balance of the fungible token, a spender account which has an allowance of the fungible token, and a receiver account with unlimited auto associations, when the token is transferred from the spender to the receiver account, then the receiver account contains the sent balance of the token and the transferred amount is debited from the holder account
4. Given an NFT, a holder account with 1 minted NFT, a spender account which has an allowance of the NFT, and a receiver account with unlimited auto associations, when the NFT is transferred from the spender to the receiver account, then the receiver account contains the NFT and the NFT is debited from the holder account (this is same as above but with NFT)
5. Given a fungible token with decimals, a sender account with a balance of the fungible token, and a receiver account with unlimited auto associations, when the token is transferred from the sender to the receiver account, then the receiver account contains the sent balance of the token
6. Given a a receiver account with auto associations set to < -1, the INVALID_MAX_AUTO_ASSOCIATIONS error should be raised for AccountCreate and AccountUpdate transactions

Related issue(s):

#2332 #2333

Fixes #

#2332 #2333

Notes for reviewer:

Checklist

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

[gsstoykov]

BTW, just for the future:

• We usually put the related issues in the Fixes section
• When you have tested a certain feature you should mark the Tested checkbox in the PR.
• The Related issues section usually contains existing repository issues. So you can move your comment from there to Notes to reviewer

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[svetoslav-nikol0v]

LGTM

[0xivanov]

LGTM