encodeType of typed data does not encode preset types correctly

[DelevoXDG]

Describe the bug
encodeType of type data does not encode preset types correctly.

You can verify this from the SNIP:

• X is an u256
• X is a TokenAmount
• X is a Nft ID

Where for every preset type, it says:

It will be encoded as the following object.

And per the X is an object, every object should encoded as follows:

escape(name) || "(" || escape(param1_name) || ":" || escape(param1_type) || "," || ... || escape(paramN_name) || ":"|| escape(paramN_type) || ")"
If the object references other objects/enum which can also reference other objects/enums, the set of referenced objects/enums is collected, sorted by name, and appended to the encoding.

The spec also refers to this repo for examples, where preset type u256 is included along with its properties.

To Reproduce
Run this test:

starknet.js/__tests__/utils/typedData.test.ts

Line 50 in fdcc7fb

`"\\"Example\\"(\\"n0\\":\\"TokenAmount\\",\\"n1\\":\\"NftId\\")"`

Expected behavior
All preset types are encoded as objects:

"Example"("n0":"TokenAmount","n1":"NftId")"NftId"("collection_address":"ContractAddress","token_id":"u256")"TokenAmount"("token_address":"ContractAddress","amount":"u256")"u256"("low":"u128","high":"u128")

Actual behavior
All preset types are encoded as basic types:

"Example"("n0":"TokenAmount","n1":"NftId")

Desktop (please complete the following information):

• Starknet.js version cb20590

[penovicp]

Note that in the current code, following the SNIP notation, encode_type is treated as a simple type but encoding is applied as for a custom type/object.

@sgc-code Could you confirm that encode_type should be applied the same as for a custom type? I recall being conflicted about this while working on #920 since either approach is essentially a constant but it seems I didn't remember to explicitly ask about it.

[github-actions]

🎉 This issue has been resolved in version 6.4.0 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 7.0.0 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀