Make a plan on how to approach categorization of used code

[yamimaio]

As per the retro action item:
There is too much to maintain. Existing code that could have been written in a more maintainable way, untested, commented, etc.

Discussion

• We should categorize what is being used and what is not.
• Everything that is not rust node, webnode, frontend can be ignored for now? No, gql should not be removed. There are other components as well that should remain.
• What we deem is not used… Do we move it? Remove from workspace manifest? Delete it?
• Should we have a different CI for tools? Should we move tools out of the workspace?
• Dockerfiles only for tools that can be removed? Some tools might be worth running on a server. We should revamp dockerfiles that are worth keeping. However, doing this might be worth doing after road to devnet and plan for mainnet.

Action Items
We want to categorize what is being used and what is not, on a per crate basis, understanding what code is for node, for testing or for tools. Make a plan to review with the team on how to approach it.

[richardpringle]

I took a look at the code and it seems that everything is actually being used. Anything that's potentially not used is in the tools/ directory. I think we just need to move node/testing into the tools directory. Any feature flags that exist outside of the tools/ directory that aren't being used should probably be deleted

[richardpringle]

waiting on #1693 to land