The MSB5009 - SolutionParseNestedProjectError has been printed for a
certain project but without specifying the project's name or even GUID
which was making this issue difficult to debug.
To make it more developer/user friendly, the MSB5009 error has been
provided with the invalid project's name and GUID embedded in the error
message.
Message is extended by string arguments separate for ProjectName and
ProjectGUID, so from now on it's required to add them as a
BuildEventFileInfo constructor arguments.

NOTE: Though error message is automaticaly generated for each language,
some are still not translated.

The extended MSB5009 error message requires ProjectName and ProjectGuid
as arguments otherwise raw "{0}" will be displayed to the console in
case of error.
The MSB5009 error messsage is used in other places than the one covered
in the extension implementation, so each place using this error has to
be covered with the changes.

NOTE: The only exception is the SolutionFile.ParseNestedProjects() method
which uses the MSB5009 error too, but at the point of calling this error,
there are no project's name nor GUID available to display, so it should
continue to use the original error message string.
To make it possible:
 - the original error string has been kept,
 - while the extended one has been renamed to
   "SolutionParseNestedProjectErrorWithNameAndGuid"
   to indicate it's extended content and required arguments

Leaving the MSB5009 error message in the original form for
SolutionFile.ParseNestedProject() method doesn't mean that no
information will be given to developer/user.
Note that it already calls the BuildEventFileInfo constructor with full
path and current line's number, which will ease the debugging in case of
having MSB5009 error.

New unit test covering the enhanced MSB5009 error checks whether:
 - MSB5009 error is thrown for incorrectly nested project in solution
 - error contains the name of incorrectly nested project
 - error contains the GUID of incorrectly nested project

NOTE: The solution file used for this unit test is the original solution
file given as an example of the original error which these changes fix.
Please see: dotnet#4835

Co-authored-by: Rainer Sigwald <[email protected]>