Evaluate whether to include the hedera-smart-contracts repo as a dependency

[acuarica]

As we are starting to include more and more HTS functionality, we need more type and interface definitions. See for example,

• feat: Implement getTokenInfo (foundry solution) #128
• fix: extended redirectForToken to support IHRC719 token association #120

Most of these definitions are already present in the hedera-smart-contracts repo. We should evaluate whether to include this repo as a dependency. One minor drawback is the import paths are quite long, for example

import {IHRC719} from "hedera-smart-contracts/system-contracts/hedera-token-service/IHRC719.sol";

This could be changed locally by adding a remapping to remappings.txt like

hedera/system/hts/=lib/hedera-smart-contracts/contracts/system-contracts/hedera-token-service/

so the above import looks like

import {IHRC719} from "hedera/system/hts/IHRC719.sol";

Note

If we adopt this solution, we need to exclude the lib/ folder from tsconfig.json to avoid unrelated type-checking issues.

Related issues to consume the smart contracts repo from an npm package

• [EPIC] npm publish repo hedera-smart-contracts#115
• npm packages for system contracts (e.g. hts) hedera-smart-contracts#1019