Bump up priority for formatting analyzer

[mavasani]

Follow-up change to #67058. We also trim down the analyzers to run for each code action priority bucket, so the analyzer priority needs to match the fixer priority. I'll add a unit test in a follow-up PR to verify that all our analyzer/fixer pairs have matching priority.

roslyn/src/Features/LanguageServer/Protocol/Features/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer_GetDiagnosticsForSpan.cs

Lines 404 to 424 in 6c98e5c

	private bool MatchesPriority(DiagnosticAnalyzer analyzer)
	{
	// If caller isn't asking for prioritized result, then run all analyzers.
	if (_priority == CodeActionRequestPriority.None)
	return true;
	// 'CodeActionRequestPriority.Lowest' is used for suppression/configuration fixes,
	// which requires all analyzer diagnostics.
	if (_priority == CodeActionRequestPriority.Lowest)
	return true;
	// The compiler analyzer always counts for any priority. It's diagnostics may be fixed
	// by high pri or normal pri fixers.
	if (analyzer.IsCompilerAnalyzer())
	return true;
	var analyzerPriority = analyzer is IBuiltInAnalyzer { RequestPriority: var requestPriority }
	? requestPriority
	: CodeActionRequestPriority.Normal;
	return _priority == analyzerPriority;
	}

[CyrusNajmabadi]

I also had a PR for this. But I guess I didn't push it last night :-).

I'm ok with this. But instead of copying the doc comment, have one of the doc comments 'inheritdoc' the other.

[mavasani]

But instead of copying the doc comment, have one of the doc comments 'inheritdoc' the other.

Thanks, I’ll make this change in a follow up PR