Document the survey process

We would like to formalize the process of creating the next-10 survey for Node.js.
The main issue is that we didnt define clearly a deadline after which the survey should not be modified.
My proposal is to document this process so that:

• One champion opens the PR with the question copy pasted from the previous
• We decide a deadline where the PR gets merged and questions cannot be added/removed (unless a reason important enough at discretion of the champion)
• Collaborators and TSC review the questions, ask for changes etc... and approve
• PR cannot be merged with changes requested, needs approval
• A test-survey is then created to make sure there are no typos, errors on the platforms used on the survey etc...
• After x days the survey goes live
• After x days the survey is closed

@kyliewd will help us to define guidelines on how to prepare a survey, (lenght, open questions etc...)

ping @nodejs/next-10

Start by reviewing the previous next-10 survey and any existing guidance for creating it. Document the champion, review and approval steps, deadlines for changes, test-survey checks, and launch and closing timing; done means the process is written clearly enough for collaborators and the TSC to follow.