[release/5.0] Add Microsoft StrongNameKey back to System.Composition*

[github-actions]

Backport of #45756 to release/5.0
Fixes #45638

/cc @ViktorHofer

Customer Impact

The changed public key token in the 5.0 package causes the CLR to not bind references even with binding redirects.

Testing

The package was produced locally and the Microsoft public key token is again used for any live built assets in the package.

Risk

Low. The package is already broken for at least customers on .NET Framework. The change only involves swapping out the public key token.

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to this area: @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Backport of #45756 to release/5.0

/cc @ViktorHofer

Customer Impact

The changed public key token in the 5.0 package causes the CLR to not bind references even with binding redirects.

Testing

The package was produced locally and the Microsoft public key token is again used for any live built assets in the package.

Risk

Low. The package is already broken for at least customers on .NET Framework. The change only involves swapping out the public key token.

Author:	github-actions[bot]
Assignees:	-
Labels:	Servicing-consider, area-System.Composition
Milestone:	-

[ViktorHofer]

release/5.0 builds failing on OSX:

Error: Not a directory @ dir_s_rmdir - /usr/local/Cellar/openssl 
Removing: /Users/runner/Library/Caches/Homebrew/openldap--2.4.55.mojave.bottle.tar.gz... (2.8MB) 
Removing: /usr/local/Cellar/openssl/1.0.2t... (1,787 files, 12.0MB) 
Installing automake has failed!

This probably started to happen in the last days as another 5.0 build 5 days ago succeeded. cc @dotnet/runtime-infrastructure

[ViktorHofer]

cc @danmosemsft or @ericstj for tactics (I can talk about this change as well - don't have a preference)

[ericstj]

This needs to include the packages in the build.

[ViktorHofer]

@Anipik 5.0 builds are failing. We should fix that.

@Anipik one more thing. Can you please let me know which changes in the infra are required to ship the System.Composition packages?

[safern]

Module @ericstj's comment that we need to include the packages to the build

[safern]

The OSX issue will be fixed by: #45809

[ViktorHofer]

After #45799 is in, I will update the PR to build the package.

[ViktorHofer]

@Anipik thanks for merging. Did you ask @ericstj if the change of the strong name key requires the assembly version to be bumped?

[ericstj]

Yes we discussed this. It's not strictly necessary. Since the strong name is changing, that's sufficient to ensure there's no clash in GAC / load on .NETFramework.