feat: add Recover functions for idiomatic panic redirects

[matfax]

The new Recover functions provide enhanced error handling capabilities that are not available in the other error helpers. They maintain Go's simplistic error return signature while adhering to functional programming idioms in which cross-scope error variable access doesn't fit.

1. Type safety: Unlike the Try functions, the new Recover functions allow for strongly typed error handling, reducing the risk of runtime type errors.

2. Granular control: Recover...Typed functions allow specifying which error types to catch, providing finer-grained control over error handling.

3. Propagation focus: Whereas the Try functions aim for a catch mechanism, the Recover functions aim for a redirect of specific panic and error types to calling scopes.

4. Callback error merging: Recover...Error functions combine both panic recovery and callback errors, simplifying error handling in complex scenarios.

5. Improved composability: These functions can be easily integrated into existing code and external library calls, enhancing the overall robustness of error handling without significant refactoring.

By providing these capabilities, the Recover functions fill a gap in error handling that the other helpers do not address, offering a more comprehensive and flexible approach to managing errors and panics.

[matfax]

@samber Any thoughts? I'm not on Twitter, so I can't ping you there.

RecoverXWithError might be a more consistent but lengthy choice for helpers with error callback.
Also, the TypedRecover could alternatively be named DeferredRecover or InlineRecover.