♻️ Leverage runtime/debug to print the full stack trace info

[panjf2000]

Description

Use Stack() in runtime/debug, not in runtime, to get the panic stack trace info cuz the one in runtime/debug is a more convenient wrapper provided by Go team to print stack trace info, see golang/go#12363, besides, the current implementation only prints the first 1024 bytes, which might result in the missing vital information in the content after 1024 bytes, and the new approach resolves this issue by printing the full stack trace info.

Type of change

Please delete options that are not relevant.

• Enhancement

Checklist:

• For new functionalities I follow the inspiration of the express js framework and built them similar in usage
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation - https://github.com/gofiber/docs for https://docs.gofiber.io/
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• If new dependencies exist, I have checked that they are really necessary and agreed with the maintainers/community (we want to have as few dependencies as possible)
• I tried to make my code as fast as possible with as few allocations as possible
• For new code I have written benchmarks so that they can be analyzed and improved

Commit formatting:

Use emojis on commit messages so it provides an easy way of identifying the purpose or intention of a commit. Check out the emoji cheatsheet here: https://gitmoji.carloscuesta.me/

[welcome]

Thanks for opening this pull request! 🎉 Please check out our contributing guidelines. If you need help or want to chat with us, join us on Discord https://gofiber.io/discord

[welcome]

Congrats on merging your first pull request! 🎉 We here at Fiber are proud of you! If you need help or want to chat with us, join us on Discord https://gofiber.io/discord