Error Standardization: Configuration API #7485 about dapr

[stackanthony]

Hey @cicoyle, so looking through predefined.go I see that there's currently 5 different config related errors set in there. Should I only focus on migrating these over to the gRPC richer error model?

	// Configuration.
	ErrConfigurationStoresNotConfigured = "configuration stores not configured"
	ErrConfigurationStoreNotFound       = "configuration store %s not found"
	ErrConfigurationGet                 = "failed to get %s from Configuration store %s: %v"
	ErrConfigurationSubscribe           = "failed to subscribe %s from Configuration store %s: %v"
	ErrConfigurationUnsubscribe         = "failed to unsubscribe to configuration request %s: %v"

[stackanthony]

Just started working on this, made a new file pkg/api/errors/config.go, looks like this

package errors

import "github.com/dapr/kit/errors"

type ConfigurationError struct {
	name string
}

func Configuration(name string) *ConfigurationError {
	return &ConfigurationError{
		name: name,
	}
}

// func (c *ConfigurationError) StoresNotConfigured() error {
// 	return c.build(
//     errors.NewBuilder(grpcCode codes.Code, httpCode int, message string, tag string)
//     )
// }

func (c *ConfigurationError) build(err *errors.ErrorBuilder, errCode string, metadata map[string]string) error {
	return err.WithErrorInfo(errors.CodePrefixConfigurationStore+errCode, metadata).Build()
}

Wanted to make sure I'm on the right track. I've been looking through the codebase and the other error models that have been standardized have been a huge help thus far. Could I get some feedback?