Re-organize issues for SOW

[thelastjosh]

This is the context of a potential contract with dOrg. They are requesting additional detail, rather than have that sit in a contract I'm going to organize those specs into public issues.

Currently:

• [50%] Create caching backend database to support explore functionality in the frontend and scalable/flexible querying of DAO*-compliant DAOs and services.
• [10%] Documentation including Swagger/ OpenAPI-compliant docs, schema docs, and other technical resources and content that can be put into the DAO* documentation. Also, helping clean up and professionalize our open-source project management / GitHub repository. Actual verbose documentation will be produced by DAO* team.
• [20%] Scripting to make it easy to deploy new reference implementations to the daostar.org Endpoint Hosting Service, via AWS Lambda.
• [20%] General improvements to the API, including input validation, fixing subgraphs and reference implementations to ensure full spec-compliance with DAO*, and adding support for all EVM chains.

Not in scope but should be converted to issues:

• The Safe’s DAO* registration (i.e. initiating a proposal on the Safe to deploy a DAO* registration contract) is out of scope, though this could constitute follow-up work to develop a Safe or Zodiac app that makes it easy to deploy a DAO* registration contract.
• Editing of the DAO* endpoint is out of scope, though this could constitute follow-up work to develop a Safe or Zodiac app that exposes the DAO* editing interface directly within the Safe.