Improve when SimplifyNames analyzer is triggered

[T-Gro]

SimplifyNames analyzer is responsible for reducing qualified names if the respective namespaces/modules are being opened.
However, it was not triggering most of the time.

This PR addresses this by reducing the lock contention of this service:

• Adding timeout to waiting on SemaphoreSlim to prevent a never ending queue of requests
• Increasing the bandwith to 3 operations at the same time
• Giving up if the lock is not obtained

On top of that, when I was debugging, the project was treated as "FSharpMiscellaneous". Which meant regular .fs files (not scripts) were not analyzed in that situation:
if document.Project.IsFSharpMiscellaneousOrMetadata && not document.IsFSharpScript

[T-Gro]

/run fantomas

[github-actions]

Ran fantomas: https://github.com/dotnet/fsharp/actions/runs/4692140323

[majocha]

On top of that, when I was debugging, the project was treated as "FSharpMiscellaneous". Which meant regular .fs files (not scripts) were not analyzed in that situation:
if document.Project.IsFSharpMiscellaneousOrMetadata && not document.IsFSharpScript

Does this happen when opening a solution with preopened documents? I've seen VS creating temporary projects for open documents, it seems it happens before the solution is fully loaded or something. Do we want to run analyzers on those?

[T-Gro]

On top of that, when I was debugging, the project was treated as "FSharpMiscellaneous". Which meant regular .fs files (not scripts) were not analyzed in that situation:
if document.Project.IsFSharpMiscellaneousOrMetadata && not document.IsFSharpScript

Does this happen when opening a solution with preopened documents? I've seen VS creating temporary projects for open documents, it seems it happens before the solution is fully loaded or something. Do we want to run analyzers on those?

I have seen it even after dozens of seconds when debugging.
Here, it is still rate-limited by the SemaphoreSlim guard.