Document for team adoption and maintenance

[BigLep]

Done Criteria

There is repo documentation that covers

• Architecture
• What/why certain technologies were chosen
• Why alternative technologies (e.g., docker compose) aren't used

Why Important

• Spreads knowledge so @redpanda-f isn’t a single point of failure for running/extending it.

User/Customer

All current and future engineers working on the FOC stack who will have to maintain this foc-localnet tool.

[redpanda-f]

We are at the verge of pushing out v1-rc which will become v1 soon. It contains both README.md and Advanced_Readme.md that documents everything properly. If issues persist, kindly consider opening new issues with specific direction of needed documentation.

[BigLep]

@redpanda-f : I agree that #16 is covering almost everything listed in the done criteria. The one exception is that I didn't see discussion about why technologies like docker compose aren't used.

Regardless though, I don't think we should issues unless the PR is reviewed and merged. Currently there is outstanding feedback that isn't addressed/merged. As a result, I'm going to reopen to be clear about the status.

[redpanda-f]

Oh yeah, just for clarity. docker-compose wan't used since it lacks the pre- and post- checks that we want to consistently keep doing between steps. Moreover, there is a need to have deterministic key generation, multiple PDP SP support etc. All of this needs machinery more complicated than docker-compose