Replace multierror.Append with errors.Join

[JonCrowther]

Issue:

Problem

The package go-multierror from here uses the MPL 2.0 license, which is considered an incompatible license in rancher.

Solution

Multierrors can be replaced with errors.Join and get similar results. Multierror is formatted a little nicer, but both combine errors and can be checked for the existence of specific errors.

Here is an example of the formatting difference:
https://go.dev/play/p/qYefpBQ81GL

While I was working on removing multierror, I also replaced https://github.com/pkg/errors with the errors standard library. Specifically, I replaced instances of errors.Wrap(err, "message") with fmt.Errorf("message: %w", err). Both wrap the error and create the same error message. The motivation behind this is that https://github.com/pkg/errors has been archived and hasn't received updates since 2020. In a future PR it should be completely removed from rancher.

It's still imported as an indirect requirement, but rancher no longer makes use of it directly.

Testing

The existing unit tests pass. This does not change functionality, just how the errors are handled.

Engineering Testing

Manual Testing

Automated Testing

• Test types added/modified:
  • Unit
  • Integration (Go Framework)
  • Integration (v2prov Framework)
  • Validation (Go Framework)
  • Other - Explain: EXPLAIN
  • None
  • REMOVE NOT APPLICABLE BULLET POINTS ABOVE
• If "None" - Reason: EXPLAIN THE REASON
• If "None" - GH Issue/PR: LINK TO GH ISSUE/PR TO ADD TESTS

Summary: TODO

QA Testing Considerations

Regressions Considerations

TODO

Existing / newly added automated tests that provide evidence there are no regressions:

• TODO

[raulcabello]

Code looks good to me. It makes sense to migrate to error.Join
Errors will now be longer as the separator for errors.Join is a new line \n instead of : , but I think that should not be a problem.

[bigkevmcd]

@JonCrowther Thanks for the play example, nice way to show the differences (I have a slight preference for the Go multi error version, I think the go-multierror one is harder to internationalise 😄 )

[brandond]

I'm curious how we started using multierror, as wrangler has https://github.com/rancher/wrangler/blob/master/pkg/merr/error.go which does similar things if you use merr.Errors and merr.NewErrors() - this package used to be the idiomatic one for use when accumulating errors.