.Net BugFix Adding Plugins.Memory to be correctly picked by code sign…

…ing (#3497)

### Motivation and Context

`SemanticKernel.Plugins.Memory` package was misconfigured in the
solution to not publish.

This ended up causing the package to not be correctly signed in the
pipeline.

Resolves #3382

The problem will be fixed in the next beta release.

### Contribution Checklist

- [x] The code builds clean without any errors or warnings
- [x] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄

dotnet/SK-dotnet.sln

@@ -397,8 +397,8 @@ Global
 		{CD24F70C-224D-4125-AED4-AFFE6F68C997}.Release|Any CPU.Build.0 = Release|Any CPU
 		{E91365A1-8B01-4AB8-825F-67E3515EADCD}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
 		{E91365A1-8B01-4AB8-825F-67E3515EADCD}.Debug|Any CPU.Build.0 = Debug|Any CPU
-		{E91365A1-8B01-4AB8-825F-67E3515EADCD}.Publish|Any CPU.ActiveCfg = Debug|Any CPU
-		{E91365A1-8B01-4AB8-825F-67E3515EADCD}.Publish|Any CPU.Build.0 = Debug|Any CPU
+		{E91365A1-8B01-4AB8-825F-67E3515EADCD}.Publish|Any CPU.ActiveCfg = Publish|Any CPU
+		{E91365A1-8B01-4AB8-825F-67E3515EADCD}.Publish|Any CPU.Build.0 = Publish|Any CPU
 		{E91365A1-8B01-4AB8-825F-67E3515EADCD}.Release|Any CPU.ActiveCfg = Release|Any CPU
 		{E91365A1-8B01-4AB8-825F-67E3515EADCD}.Release|Any CPU.Build.0 = Release|Any CPU
 		{4CA6B046-DFE1-417C-A4A0-43BFD262C681}.Debug|Any CPU.ActiveCfg = Debug|Any CPU