Implement AOS-47: Additional Error Specification

[xxchan]

rendered proposal

implement AOS-51 together beyondstorage/specs#51

• update go-storage: Implement AOS-47 Additional Error Specification  #555 Implement AOS-51: Distinguish Errors by IsAosError #564

go-service-*:

first update dependency: go get -d github.com/aos-dev/go-storage/v3@master

AOS-47:

• Turn ad-hoc string errors into defined errors: check rg "(fmt.Errorf)|errors\.New"
• Turn SDK errors into fmt.Errorf("%w, %v", services.ErrUnexpected, err)
• Return error structs instead of pointers:
  • rg -l "Error" | xargs sed -i 's/&\(.*\)Error/\1Error/g'
  • rg -l "Error" | xargs sed -i 's/New\(.*\)Error(\(.*\))/\1Error{\2}/g'
• Check naming convention

AOS-51:

• use errorCode : rg -l "errors\.New" | xargs sed -i 's/errors\.New/services.NewErrorCode/g'
• check AosError in formatError: add this

	if _, ok := err.(services.AosError); ok {
		return err
	}

• add formatError in InitError's Err field:
  • update newServicerAndStorager
  • rg -l InitError | xargs sed -i 's/InitError\(.*\)Err: err/InitError\1Err: formatError(err)/g'

---

• azblob
• cos
• dropbox
• fs
• gcs
• kodo
• oss
• qingstor
• s3
• uss

[Xuanwo]

• Please also update go-service-example

[Xuanwo]

Let's add a doc about error handling in go-storage? Tell the user what's our design and how could they use it.