It appears that we might not be passing along the powershell.scriptAnalysis.settingsPath setting to PSScriptAnalyzer in the language service. This is likely caused by the recent changes to our PSScriptAnalyzer integration so I'll just need to wire that back up.