ARTESCA-16170: Initialize an error library for golang

[anthony-treuillier-scality]

No description provided.

[eg-ayoub]

I think if this is our functional replacement for Wrap, we should add a
WithDetailf function

    func (e *Error) WithDetailf(format string, args ...any) *Error {
        return e.WithDetails(fmt.Sprintf(string, args))

[anthony-treuillier-scality]

done

[vdaviot]

To me this doesn't replace wrap.
This have to be called on an already created error from the lib, which defy the purpose of wrapping in the first place IMHO

Looking at the previous implementation, the logic difference is clear:

func Wrap(err error, message string) error {
	if err == nil {
		return nil
	}
	err = &withMessage{
		cause: err,
		msg:   message,
	}
	return &withStack{
		err,
		callers(),
	}
}

---

But I'm all in for @eg-ayoub's suggestion

[eg-ayoub]

I see it from a end purpose point of view,
wrap and wrapf supplement the output of Error()
and with the details object, that purpose is fulfilled, cf. Error() lines 154 to 161

[vdaviot]

To me this doesn't replace wrap.
This have to be called on an already created error from the lib, which defy the purpose of wrapping in the first place IMHO

Looking at the previous implementation, the logic difference is clear:

func Wrap(err error, message string) error {
	if err == nil {
		return nil
	}
	err = &withMessage{
		cause: err,
		msg:   message,
	}
	return &withStack{
		err,
		callers(),
	}
}

---

But I'm all in for @eg-ayoub's suggestion