Clarify that `Publish*` properties can make apps not debuggable by default

Context: https://github.com/dotnet/runtime/issues/45382#issuecomment-968600238

`dotnet publish` with various `Publish*` properties can make an app not debuggable. However, some people use `publish` as part of their workflow.

This applies to:

- `PublishSingleFile`
- `PublishAot`

There are two approaches to resolving this:

```xml
true
```

or (something like)

```
true
```

We should do the following:

- Ensure that Native AOT and Single File docs cover debugging UX / expectations.
- Document the pattern for making `Publish*` properties opt-in (with one or both of the patterns above) with `dotnet publish` in the publish docs.
- Link between the pages.

@hoyosjs @agocke @jkotas @samsp-msft

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 8ee36626-0fc2-20d8-81c5-a3cd212244b2
* Version Independent ID: 044ba93c-9ad9-80c7-dc5c-27a80c9bd921
* Content: [Publish apps with the .NET CLI - .NET](https://docs.microsoft.com/en-us/dotnet/core/deploying/deploy-with-cli)
* Content Source: [docs/core/deploying/deploy-with-cli.md](https://github.com/dotnet/docs/blob/main/docs/core/deploying/deploy-with-cli.md)
* Product: **dotnet-fundamentals**
* GitHub Login: @adegeo
* Microsoft Alias: **adegeo**