AWS Toolkit fails to publish projects having a unique name within solutions.

## Description

Elastic Beanstalk fails to deploy when publishing a project that is part of a DotNet Core Solution with a different name than the project.

## Reproduction Steps

Create a solution with multiple projects. Name each project differently than the solution. For instance, a solution named SampleProject with SampleProject.API, SampleProject.Ideneity, and SampleProject.Data.

Publish one of the projects to and EC2 instance using the AWS. The project will fail to publish because it is looks for SampleProject.dll, which doesn't exist.

### Logs

2020/07/13 03:30:15.635659 [ERROR] An error occurred during execution of command [app-deploy] - [CheckProcfileForDotNetCoreApplication]. Stop running the command. Error: error stat /var/app/staging/SampleProject.dll: no such file or directory with file /var/app/staging/SampleProject.dll

### Environment

Version 1.18.0.0
Dot Net Core App 3.1.3
Windows 10
Visual Studio 2019

## Resolution

Create an empty dummy app with the same name as the solution to satisfy the missing file error.

[Here is a related StackOverflow question with the same issue, and a workaround.](https://stackoverflow.com/questions/62698712/codepipeline-elasticbeanstalk-error-an-error-occurred-during-execution-of-comm)

---

This is a :bug: bug-report

Start with the Elastic Beanstalk deployment path and the CheckProcfileForDotNetCoreApplication step named in the log; compare the solution name with the published project's assembly name. Reproduce with a multi-project .NET Core 3.1 solution, then verify publishing the differently named project no longer looks for the solution-named DLL.

Written by the indexing model from the issue text.