Feat: should we continue to force errors.Errorf()?

[rchincha]

Discussed in #376

^{Originally posted by hallyn December 19, 2022}
The errors package has been "archived" (pkg/errors#245). errors.Wrapf() is supposed to be replaced by fmt.Errorf("%w"). However, (1) %w output is not liked by some, and more importantly (2) fmt.Errorf does not yet support a way to add a stack trace, which was the original reason for requiring errors.Errorf() in the stacker package.

What should be the official guidance right now? Should we continue recommending/requiring the errors package, or switch?

[hallyn]

IMO continuing to use errors.Wrapf is the sanest way. It gives the most useful output.