PDB symbol path don't add up when debugging (attaching) Azure Functions inside a container

It looks like the paths don't match when you attach to a running container hosting Azure Functions.

Steps to reproduce:
1. Follow steps 1 to 3 in this guide: https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-function-linux-custom-image?tabs=isolated-process%2Cbash%2Cazure-cli&pivots=programming-language-csharp
2. Put a break-point in VS Code in the Test Function
3. Attach to the container through VS Code (see luanch.json below)
The following error occurs:


The problem seems to be in [Dockerfile.dotnet](https://github.com/Azure/azure-functions-core-tools/blob/dev/src/Azure.Functions.Cli/StaticResources/Dockerfile.dotnet) where it copies to source `COPY . /src/dotnet-function-app`. Changing it to `COPY . /src` seems to fix the issue. (I don't know if it will have other implications)

_luanch.json_
```json
{
"version": "0.2.0",
"configurations": [
{
"name": "Docker .NET Core Attach",
"type": "docker",
"request": "attach",
"platform": "netCore",
"sourceFileMap": {
"/src": "${workspaceFolder}/src/scanner-api"
}
}
]
}
```

Start with src/Azure.Functions.Cli/StaticResources/Dockerfile.dotnet and compare its COPY destination with the /src mapping in the launch.json example. Reproduce the container attach workflow from the linked Azure Functions guide, then verify whether the proposed path alignment restores breakpoint and PDB resolution without affecting other image behavior.

Written by the indexing model from the issue text.