[Feature][Framework] Enforce errors.Error interface usage throughout backend code

[keon94]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

#2134 introduced a new error interface with an extended API. The existing function signatures however use the native golang error interface. Replace them all with errors.Error. This way the code becomes more self-documenting and forces developers to use the new error API.

Use case

Use errors.Error in the API signatures.

Related issues

#2134

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[keon94]

tip: Using this Regex/Replace will take care of transforming most if not all function signatures (except lambdas):
regex: (^(func|)\s+?(\(.*?\)|)\s*[A-Za-z_0-9]+?\(.*\).*?)(error)([\s|,|\)].*$)
regex(only exported): (^(func|)\s+?(\(.*?\)|)\s*[A-Z][A-Za-z_0-9]+?\(.*\).*?)(error)([\s|,|\)].*$)
sub: $1errors.Error$5

[keon94]

PR: #2941