Update CHANGELOG to reflect mandatory FileGroup parameter in New-SqlDscDataFile; add suppression for ScriptAnalyzer warning in function

Author: johlju

CHANGELOG.md

@@ -38,8 +38,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   Server FileGroups. This command simplifies creating DataFile objects with
   specified physical file paths, supporting both regular database files (.mdf, .ndf)
   and sparse files for database snapshots (.ss). The `FileGroup` parameter is
-  optional, allowing DataFile objects to be created standalone and assigned to a
-  FileGroup later.
+  mandatory, requiring DataFile objects to be created with an associated FileGroup.
 - Added public command `Add-SqlDscDataFile` to add an existing DataFile object
   to a FileGroup. This command provides a clean way to associate DataFile objects
   with FileGroups after they have been created.

source/Public/New-SqlDscDataFile.ps1

@@ -45,6 +45,7 @@
 #>
 function New-SqlDscDataFile
 {
+    [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute('UseSyntacticallyCorrectExamples', '', Justification = 'Because the rule does not yet support parsing the code when a parameter type is not available. The ScriptAnalyzer rule UseSyntacticallyCorrectExamples will always error in the editor due to https://github.com/indented-automation/Indented.ScriptAnalyzerRules/issues/8.')]
     [CmdletBinding(SupportsShouldProcess = $true, ConfirmImpact = 'High')]
     [OutputType([Microsoft.SqlServer.Management.Smo.DataFile])]
     param