Serverless applications with multiple .NET projects

**Describe the bug**
[This AWS developer blog](https://aws.amazon.com/blogs/developer/aws-serverless-applications-with-multiple-net-core-projects/) explains how we can have multiple .NET projects to host different Lambda functions, and point the serverless template to each project. The blog shows that we can have the serverless template live in the solution folder, rather than a project-specific folder.

I've done something similar in my repo, however when I try to use the `AWS Lambda .NET Core Deployment` in Azure DevOps, the task does not appear to support having the serverless template live in the solution folder. The task **requires** a path to a **single** project that hosts a Lambda function and the serverless template. This doesn't satisfy the use case where Lambda functions reside across multiple projects.

Is there a way to workaround this, or plan to support it?

**Expected behavior**
For the task to support multiple projects.

**Your Environment**
- Azure Devops

Start with the AWS Lambda .NET Core Deployment task and its project and serverless-template path inputs, then compare them with the described solution-level template layout. Done means the task supports Lambda functions across multiple .NET projects from a shared serverless template, or documents a supported workaround.

Written by the indexing model from the issue text.