Add support for DATA_COMPRESSION and SORT_IN_TEMPDB SQL Server index options

[hmajerus]

Closes #30408

Please check whether the PR fulfills these requirements

• I've read the guidelines for contributing and seen the walkthrough
• I've posted a comment on an issue with a (loosely) detailed description of how I am planning to contribute and got approval from a member of the team
• The code builds and tests pass locally (also verified by our automated build checks)
• Commit messages follow this format:

        Summary of the changes
        - Detail 1
        - Detail 2

        Fixes #bugnumber

• Tests for the changes have been added (for bug fixes / features)
• Code follows the same patterns and style as existing code in this repo

[hmajerus]

@dotnet-policy-service agree company="Buildertrend"

[hmajerus]

@ajcvickers and/or @bricelam Sorry for the ping, but let me know if there is anything I can provide or do to make this PR more manageable to review. I have the time to account for any recommendations you may have.

[bricelam]

This design looks good to me.

I want @AndriySvyryd to review the metadata changes.

You're also missing the logic to put this in the migrations model snapshot. Without it, you'll keep getting drop-creates every migration. I think that logic lives here:

efcore/src/EFCore.SqlServer/Design/Internal/SqlServerAnnotationCodeGenerator.cs

Lines 335 to 346 in afef2e5

	protected override MethodCallCodeFragment? GenerateFluentApi(IIndex index, IAnnotation annotation)
	=> annotation.Name switch
	{
	SqlServerAnnotationNames.Clustered => (bool)annotation.Value! == false
	? new MethodCallCodeFragment(IndexIsClusteredMethodInfo, false)
	: new MethodCallCodeFragment(IndexIsClusteredMethodInfo),
	SqlServerAnnotationNames.Include => new MethodCallCodeFragment(IndexIncludePropertiesMethodInfo, annotation.Value),
	SqlServerAnnotationNames.FillFactor => new MethodCallCodeFragment(IndexHasFillFactorMethodInfo, annotation.Value),
	_ => null
	};

[hmajerus]

Cool, I'm busy here at the end of the week, but will get to fixing that next week.

[bricelam]

No rush, sorry it took us so long to get to

[hmajerus]

Updated to use SqlServerIndexBuilderExtensions for DataCompression and SortInTempDb in snapshots.

Want to point out that without that update the snapshots would still contain something that looks like this:

b.HasIndex("Id").HasAnnotation("SqlServer:DataCompression", DataCompressionType.Row);

Which will prevent those drop-creates. This is currently the case for the IsCreatedOnline Index option.

This update makes the snapshot look like the following, which I imagine is preferred to the one above anyway.

SqlServerIndexBuilderExtensions.UseDataCompression(b.HasIndex("Id"), DataCompressionType.Row);