Remote Debugging On Linux Arm instructions are incorrect for FDD

## Environment data
Not Applicable

## Steps to reproduce

Follow the steps in he [Remote Debugging On Linux Arm](https://github.com/OmniSharp/omnisharp-vscode/wiki/Remote-Debugging-On-Linux-Arm#build-and-deploy) documentation page to do a Framework Dependent Deployment. Check that you can debug the sample console application.

Add a reference to a NuGet package and make use of that package in the sample code.

Try to debug the new version of the sample console application.

## Expected behaviour

Able to debug into your code both with the original sample console application and the extended console application.

## Actual behavior

Able to debug into the original sample application but not into the extended version. See errors regarding assemblies missing e.g.
```
An assembly specified in the application dependencies manifest (MyConsoleApp.deps.json) was not found:
package: 'System.Text.Encoding.CodePages', version: '4.4.0'
path: 'lib/netstandard2.0/System.Text.Encoding.CodePages.dll'
The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use .NET Core. This may be expected if the target process did not run on .NET Core.
```

The documentation appears to be wrong for Framework Dependent Deployment. It should use `dotnet publish` rather than `dotnet build` and the contents of the `bin/Debug/netcoreapp2.1/publish` directory should be copied to the `Linux-arm` device. If you use only `dotnet build`, you don't get a `publish` directory, and if you only use the contents of the `bin/Debug/netcoreapp2.1` you only have your own assembly, not any referenced assemblies... hence the load error.

I had at first thought this was a dotnet/cli#9039 problem!

I'll look to create a pull request later.