Don't stomp on CreateSatelliteAssembliesDependsOn property in the common targets

[baronfel]

We missed this one in #4922, currently the CreateSatelliteAssembliesDependsOn definition isn't extendable by users in their project files, so they have to reach for mechanisms like Directory.Build.targets to ensure they can extend the process.

[JanKrivanek]

This actually seems to be much more widespread - e.g. the externally documented Commonly overridden DependsOn properties

• BuildDependsOn :

  msbuild/src/Tasks/Microsoft.Common.CurrentVersion.targets

  Lines 891 to 895 in 23f7752

  	<BuildDependsOn>
  	BeforeBuild;
  	CoreBuild;
  	AfterBuild
  	</BuildDependsOn>

• CleanDependsOn:

  msbuild/src/Tasks/Microsoft.Common.CurrentVersion.targets

  Lines 5675 to 5682 in 23f7752

  	<CleanDependsOn>
  	BeforeClean;
  	UnmanagedUnregistration;
  	CoreClean;
  	CleanReferencedProjects;
  	CleanPublishFolder;
  	AfterClean
  	</CleanDependsOn>

• CompileDependsOn:

  msbuild/src/Tasks/Microsoft.Common.CurrentVersion.targets

  Lines 3595 to 3607 in 23f7752

  	<CompileDependsOn>
  	ResolveReferences;
  	ResolveKeySource;
  	SetWin32ManifestProperties;
  	FindReferenceAssembliesForReferences;
  	_GenerateCompileInputs;
  	BeforeCompile;
  	_TimeStampBeforeCompile;
  	_GenerateCompileDependencyCache;
  	CoreCompile;
  	_TimeStampAfterCompile;
  	AfterCompile;
  	</CompileDependsOn>

But there are others then seem as potentially usefull - CoreBuildDependsOn, RebuildDependsOn, RunDependsOn, PublishDependsOn etc. etc.

So the questions is - do we want to generally open this? Or any of them? Or do we want to keep them as-is semi-hidden, overridable only via explicit importing of sdk.targets?

cc @baronfel

[baronfel]

Oof. IMO we should open these as #4922 intended.

[JanKrivanek]

#9755