Document ENSNode Deployments

[lightwalker-eth]

Let's please collect all the details about ENSNode deployments so that they are documented in a single "evergreen" document.

For now, suggest creating a new page in our Wiki for it. We can look to move all our Wiki content somewhere else later.

This wiki page should document ideas including:

1. Ideas here: Change Railway autodeployments to non-main branch #47 (comment)
2. URLs for endpoints
   1. Ponder endpoint
   2. Subgraph compatible endpoint
3. Please also document our ENSRainbow deployment at api.ensrainbow.io

[BanaSeba]

Adding ideas coming from Slack considering additional ENSNode documentation:

Creating a totally new PR thats focused on these documentation refinements. Here you might restructure the documentation a bit based on specific audiences:

• Contributing Developers (people who are actively developing the various apps in our monorepo)
• Deployers (people who just want to run their own instances of our apps, but aren't actively working to make their own code changes).
• Additionally, for this new documentation-based PR, suggest you consider moving these ideas out of the README.md files and instead:

Putting virtually all the content into the documentation websites under the /docs directory of the monorepo. Here you can write the content as .mdx files, which is an extension of regular markdown. Whenever you create a PR for updates to the /docs directory, Vercel will create a preview environment for it The content published there ultimately goes live under https://ensnode.io/ and https://ensrainbow.io/
In the README.md files including a link to the content hosted under https://ensnode.io/ or https://ensrainbow.io/ that goes into more detail on a particular topic. In other words, please continue to make "Getting Started" like content easily discoverable in the README.md files. We should still have a section heading for these ideas. But all the details should not live in the README.md file. Instead they should live under one of the /docs sites and be linked to from the README.md files.