Smart Contract Repo Reorder/cleanup [NEEDS DESIGN]

[Ferparishuertas]

The idea is to agree on repo structure, cleanup before implementing a library, and deployment cycle.

Steps to achieve this:

• Cleat out questions
• Design repot structure
• Implement the restructure

Open questions

• why do we have a local.env published?
• why do we have a scripts folder with network freeze example?
• Why do we have an Openzeppelin folder instead using the node library?
• Why do we have libs folder vs using node libraries?
• Why tests include mixed scenarios vs
• Do we have samples for everything
• WHy Ihederatokenservice has all, but then we have HIP interfaces, Shall we inheritate?
  Enhancements Suggestions
• Should we have a Readme file per folder that explains it concepts?
• Should we have a main README more detailed to explain all the things included in the repo?
• Should me have parent folder, distinguihung system contracts activities vs other examples tools?
• Should me move samples that are smart contract functionalities more than json-rpc related stuff to the new strucuture?

[Nana-EC]

@quiet-node had a suggestion to make the https://github.com/hashgraph/hedera-smart-contracts/tree/main/contracts/system-contracts stand out more. Move other items under a sub folder of say https://github.com/hashgraph/hedera-smart-contracts/tree/main/contracts/examples
@Ferparishuertas agreed

[Nana-EC]

Goal would be https://github.com/hashgraph/hedera-smart-contracts/tree/main/contracts/system-contracts would be the folder that is included in the npm package that developers can import and utilize.
Examples under here should also be moved out to make it easier on developer experience

[Nana-EC]

@acuarica suggested we consider a separate repo to highlight system contracts even more. There's potential to make usage with other tools easier.

Q: Would this also be satisfied by a sub package