Add option to specify for roslyn server the razor output directory path

[maryamariyan]

• Adds devKitRazorOutputPath option
• Allows RazorSourceGenerator to be picked up by tooling rather than SDK
• Fixes WorkItem 1926900 (https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1926900)

/cc @CyrusNajmabadi @davidwengier @dibarbet Related to https://github.com/dotnet/roslyn/pull/72482

[maryamariyan]

Tested changes again for VS code and confirmed the problem goes away when project is targeting 6.0 and using 6.0 SDK.

Before change:

After change:

[maryamariyan]

The roslyn server version in vscode-csharp is not updated to a version that contains the server side change yet causing the failure on the CI.

[stderr] Unrecognized command or argument '--razorSourceGenerator'.
Unrecognized command or argument '/mnt/vss/_work/1/s/.razor/Microsoft.CodeAnalysis.Razor.Compiler.dll'.

Thanks @dibarbet for clarifying this

[ryzngard]

/azp run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).