testing/fuzz.go:put the new corpus that caused the panic into another folder

[pic4xiu]

I think it is better to put the corpus that caused the panic into a new folder:

• Because I try to put many corpora into my folder, the fuzz program will also put the corpus that caused the panic in it .
• Secondly, every time the fuzz program is restarted, the folder will be traversed again, which causes me to extract the file that caused the panic last time every time I fuzz.

[gopherbot]

This PR (HEAD: c7f649a) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/go/+/503358 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

[gopherbot]

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
A maintainer will review your change and provide feedback. See
https://go.dev/doc/contribute#review for more info and tips to get your
patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11 or adds a tag like "wait-release", it means that this CL will be
reviewed as part of the next development cycle. See https://go.dev/s/release
for more details.

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/503358.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Bryan Mills:

Patch Set 1: Hold+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/503358.
After addressing review feedback, remember to publish your drafts!