Add all grpc error types and error matching used by Moby.

Signed-off-by: Derek McGowan <derek@mcg.dev>

Signed-off-by: Derek McGowan <derek@mcg.dev>

Add more grpc types

By having seperate packages, users can consume base package without pulling
gRPC or HTTP as a dependency if not required.

Signed-off-by: Austin Vazquez <macedonv@amazon.com>

Split gRPC and HTTP error utility into seperate packages

The function for the interface should be `Cancelled` not `ErrCancelled`.

Signed-off-by: Derek McGowan <derek@mcg.dev>

Signed-off-by: Derek McGowan <derek@mcg.dev>

Signed-off-by: Derek McGowan <derek@mcg.dev>

Signed-off-by: Derek McGowan <derek@mcg.dev>

Add stack support

When an error object is returned and must be resolved to a single return
error, the first error matching one defined by this package should be
returned.

Signed-off-by: Derek McGowan <derek@mcg.dev>

Add a resolve error function to return first error

Add a function to each defined error to set a custom message.

Signed-off-by: Derek McGowan <derek@mcg.dev>

Add support for custom error messages

The Is interface may be used to resolve if no other unwrap interface is
implemented. This interface is safe to use in this situation, unlike
errors.Is, since the error should not be unwrapped further.

Signed-off-by: Derek McGowan <derek@mcg.dev>

When multiple errors are given, use details to encode errors into the
grpc status and decode details back into errors.

Signed-off-by: Derek McGowan <derek@mcg.dev>

Add support for grpc error details and multiple errors

Add test and fix missing definition

Signed-off-by: Derek McGowan <derek@mcg.dev>

Complete interface definitions for errors