added 'FAQ' section, including listing ~10 notable sample changes since the original vgo proposal; also cover the recent changes to 'go mod' (in the FAQ only for now)
I had previously added 'go mod -sync' as a step for the 'Preparing a release' section. Given that, updated step #3 in 'Defining a module' section: rather than 'go mod -sync', say 'go build ./...', which seems more to be the norm (e.g., based on spot checking a couple recent rsc examples). Overall, this section could still be improved/clarified.
for real this time: add first version of a new 'Preparing for a release' section to capture some recommendations/best practices and give people a place to add more recommendations
prefer 'go test all' over the older text using 'go test ...'; mention 'go build' and friends will add dependencies and update go.mod as needed; tweak step #3 in 'Defining a Module', though still could use some more clarification
updated existing mention of #26238 to indicate it is now closed; added mention of 'go get -u=patch'; added benefit of running 'go test ...' after upgrading; added mention of 'go help module-get'
added additional links to external resources; added sentence on -sync flag (taken from 'go help mod', though that step #3 could likely use more clarification); renamed the 'New Project Setup' section given it was describing steps for an existing project
