Fix for 4819285, adding setting to prevent generated project files to include SET ANSI_NULLS OFF

[allancascante]

Description

When using a SQL project (.sqlproj) as the source for schema compare instead of a .dacpac, the generated publish script includes unwanted SET ANSI_NULLS OFF commands before each object's CREATE statement. This occurs because the SDK's Sdk.props did not define default AnsiNulls or QuotedIdentifier metadata on Build items, causing DacFx to interpret the missing values as OFF. This fix adds an ItemDefinitionGroup in Sdk.props that defaults AnsiNulls and QuotedIdentifier to On for all Build items, matching the behavior of traditional SSDT projects and the behavior when using a .dacpac as source. A new test (VerifyBuildItemDefaultAnsiNullsOn) validates that Build items carry the correct default metadata. Fixes #172.

Code Changes

• Unit tests are added, if possible
• Existing tests are passing
• New or updated code follows the guidelines here
• Ensure .dacpac from changes to Microsoft.Build.Sql build process MUST be backwards compatible with older versions of SqlPackage
• Use proper logging for MSBuild tasks

[llali]

@allancascante please close this if not needed anymore