feat: Added recovery handler

[flc1125]

📑 Description

I can define a general or global recovery that catches system-level exceptions and identifies those that can be reported.

Example: unit test，

✅ Checks

• My pull request adheres to the code style of this project
• All the tests have passed

[codecov]

Codecov Report

Patch coverage: 93.58% and project coverage change: +0.15 🎉

Comparison is base (989ae8b) 62.76% compared to head (6b61843) 62.91%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #231      +/-   ##
==========================================
+ Coverage   62.76%   62.91%   +0.15%     
==========================================
  Files         128      130       +2     
  Lines        8314     8345      +31     
==========================================
+ Hits         5218     5250      +32     
  Misses       2735     2735              
+ Partials      361      360       -1     

Impacted Files	Coverage Δ
schedule/service_provider.go	0.00% <0.00%> (ø)
support/database/database.go	79.31% <0.00%> (ø)
contracts/foundation/service_provider.go	50.00% <50.00%> (ø)
support/debug/recovery/panic_handler.go	50.00% <50.00%> (ø)
schedule/application.go	94.33% <100.00%> (+1.15%)	⬆️
schedule/event.go	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[hwbrzzl]

Thanks for your PR, please add the Review Ready label when this PR can be reviewed.

[hwbrzzl]

Q: Can you please give an example for how to use this in goravel/goravel?

[flc1125]

It involves my another discussion: goravel/goravel#209

My idea is to have a Kernel to start the entire application, and this startup is a root command.

I can configure the recovery from this root command.

[hwbrzzl]

Okay, let's discuss it at goravel/goravel#209

[flc1125]

Since this discussion(goravel/goravel#209) is closed, this one is closed as well. But if there are new ideas, we can always continue to discuss them.

Welcome, everybody.