Move Command Data Files from Engine\Settings -> Engine\CommandDataFiles.

Previously they were mixed in with the Settings Preset files. This wasn't an issue as all settings file were always PSD1 and these command data files are JSON. If we are to support other settings file formats, then we need to separate these.

They are now copied to a CommandDataFiles directory in the built module. Two rules load these and will need to be fixed up to load them from the new directory:

- Rules/AvoidOverwritingBuiltInCmdlets.cs
- Rules/UseCompatibleCmdlets.cs

Author: liamjpeters

Engine/Settings/core-6.1.0-linux-arm.json renamed to Engine/CommandDataFiles/core-6.1.0-linux-arm.json

@@ -254,6 +254,9 @@ function Start-ScriptAnalyzerBuild
         $settingsFiles = Get-Childitem "$projectRoot\Engine\SettingsPresets" | ForEach-Object -MemberName FullName
         Publish-File $settingsFiles (Join-Path -Path $script:destinationDir -ChildPath Settings)
 
+        $settingsFiles = Get-Childitem "$projectRoot\Engine\CommandDataFiles" | ForEach-Object -MemberName FullName
+        Publish-File $settingsFiles (Join-Path -Path $script:destinationDir -ChildPath CommandDataFiles)
+
         $rulesProjectOutputDir = if ($env:TF_BUILD) {
             "$projectRoot\bin\${buildConfiguration}\${framework}" }
         else {