Update FSharp.Analyzers.SDK to 0.32.0 and Ionide.Analyzers to 0.14.6

[TheAngryByrd]

Follow up from:

• Add project options to analyzer contexts FSharp.Analyzers.SDK#236
• Update FSharp.Analyzers.SDK 0.32.0 and Fixed ReturnStructPartialActivePatternAnalyzer ProjectOptions when using TransparentCompiler in EditorContext ionide-analyzers#152

[Copilot]

Pull Request Overview

This PR updates the FSharp.Analyzers.SDK and Ionide.Analyzers to newer versions and adjusts the code to pass project options through the analyzer invocation pipeline.

• Bump SDK and analyzer package versions in dependencies and tool manifest
• Change runAnalyzers and fileChecked event to accept and propagate CompilerProjectOption
• Extend the editor context in Commands to include new ProjectOptions

Reviewed Changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.

File	Description
src/FsAutoComplete/LspServers/AdaptiveServerState.fs	Update fileChecked event signature and runAnalyzers to include CompilerProjectOption and derive AnalyzerProjectOptions
src/FsAutoComplete.Core/Commands.fs	Add projectOptions to analyzer context creation
paket.dependencies	Bump Ionide.Analyzers to 0.14.6 and FSharp.Analyzers.SDK to 0.32.0
.config/dotnet-tools.json	Update fsharp-analyzers tool to version 0.32.0

Comments suppressed due to low confidence (4)

src/FsAutoComplete/LspServers/AdaptiveServerState.fs:526

• No tests have been updated to cover the new runAnalyzers overload that accepts CompilerProjectOption. Consider adding unit tests to verify that both BackgroundCompilerOptions and TransparentCompilerOptions paths produce correct AnalyzerProjectOptions and invoke analyzers as expected.

  let runAnalyzers

src/FsAutoComplete/LspServers/AdaptiveServerState.fs:545

• Add an XML or inline comment explaining the purpose of analyzerOptions and how it maps from CompilerProjectOption to AnalyzerProjectOptions to help future maintainers understand this transformation.

          let analyzerOptions =

src/FsAutoComplete/LspServers/AdaptiveServerState.fs:583

• [nitpick] The fileChecked event now starts with projectOptions before the parse results, which differs from the ordering in fileParsed. Consider aligning parameter order or documenting the tuple fields clearly to maintain consistency and reduce confusion.

    <| fileChecked.Publish.Subscribe(fun (projectOptions, parseAndCheck, volatileFile, ct) ->

src/FsAutoComplete.Core/Commands.fs:1162

• [nitpick] Consider validating or handling the projectOptions value before storing it in the editor context to ensure downstream analyzers always receive a valid configuration object.

        ProjectOptions = projectOptions }