Compilers generated code isn't validated in CI when only source generators are changed

[Youssef1313]

Validation is conditioned on compilerChange being true here:

roslyn/azure-pipelines.yml

Lines 237 to 245 in 35ac8cb

	displayName: Generate Syntax Files
	inputs:
	filePath: eng/generate-compiler-code.ps1
	arguments: -test -configuration Release
	condition: or(ne(variables['Build.Reason'], 'PullRequest'), eq(variables['compilerChange'], 'true'))
	- script: $(Build.SourcesDirectory)\.dotnet\dotnet.exe tool run dotnet-format whitespace $(Build.SourcesDirectory)\src --folder --include-generated --include $(Build.SourcesDirectory)\src\Compilers\CSharp\Portable\Generated\ $(Build.SourcesDirectory)\src\Compilers\VisualBasic\Portable\Generated\ $(Build.SourcesDirectory)\src\ExpressionEvaluator\VisualBasic\Source\ResultProvider\Generated\ --verify-no-changes
	displayName: Validate Generated Syntax Files
	condition: or(ne(variables['Build.Reason'], 'PullRequest'), eq(variables['compilerChange'], 'true'))

which is run only if there are changes to src\Compilers or src\Dependencies:

roslyn/azure-pipelines.yml

Lines 206 to 208 in 35ac8cb

	include:
	- src/Compilers/*
	- src/Dependencies/*

If a PR has changes only to the generators, the validation will be incorrectly skipped

[jasonmalinowski]

@jmarolf It looks like that condition might go back to #62797 -- is just adding the additional folder to the list that was called out here sufficient, or does more work need to be done? I don't mind sending out the PR if it's a trivial fix but if this takes more work I'm not sure if you should pick this one up? (Or I'll need some explanation of how it works!)