Added codes to messages

[MichalPavlik]

Fixes #329

CONTAINER1xxx: HTTP or local daemon related failures
CONTAINER2xxx: Invalid/missing data related failures
CONTAINER3xxx: Docker process related failures

[vlada-shubina]

Just to double check, are logged errors,

sdk-container-builds/Microsoft.NET.Build.Containers/Tasks/CreateNewImage.cs

Line 63 in cbaba1c

Log.LogError($"Couldn't find matching base image for {0} that matches RuntimeIdentifier {1}", sourceImageReference.RepositoryAndTag, ContainerRuntimeIdentifier);

for example, to be done in separate PR?

[MichalPavlik]

Just to double check, are logged errors,

sdk-container-builds/Microsoft.NET.Build.Containers/Tasks/CreateNewImage.cs

Line 63 in cbaba1c

Log.LogError($"Couldn't find matching base image for {0} that matches RuntimeIdentifier {1}", sourceImageReference.RepositoryAndTag, ContainerRuntimeIdentifier);

for example, to be done in separate PR?

I would do it in separate PR.

[baronfel]

I made an issue for the remaining work

[baronfel]

@MichalPavlik were you able to check that these show nicely in VS when they are triggered?

[rainersigwald]

Not directly related to this PR but why are we using the old designer generation here, rather than the MSBuild-integrated one that works everywhere and doesn't require this stuff to be checked in?

[MichalPavlik]

Do you mean GenerateResource task? Good question. Does it generate also properties matching resource names? I have to take a look.

[rainersigwald]

Yes, it can (but it's a bit of a pain to turn it all on today: dotnet/msbuild#4751).

[baronfel]

We're going to merge this even though the messages don't show the way we want in VS's error pane. This still gives us a good foundation to build on in terms of resources and error codes, and we'll log any further work necessary after consult with @vijayrkn and @anvillan.