Fix dispose pattern in PQC types

[vcsjones]

I don't think we have been following the dispose pattern correctly for a few of the PQC implementations. We should only call managed dispose methods if disposing is true.

Technically we should also be calling the base implementation, even though they do nothing right now.

This makes the dispose pattern usage more consistent with other cryptographic algorithms.

[Copilot]

Pull Request Overview

This PR ensures that the dispose pattern in several PQC implementations follows the correct guidelines by calling managed dispose methods only when disposing is true and by invoking the base.Dispose method consistently. Key changes include:

• Adding base.Dispose(disposing) in multiple Dispose methods.
• Wrapping managed dispose calls with the disposing check in some implementations.
• Standardizing the dispose pattern across different cryptographic types.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
src/libraries/System.Security.Cryptography/src/System/Security/Cryptography/SlhDsaImplementation.OpenSsl.cs	Added base.Dispose(disposing) but still missing the disposing check when calling _key?.Dispose().
src/libraries/Common/src/System/Security/Cryptography/MLKemCng.Windows.cs	Added base.Dispose(disposing) but did not wrap _key.Dispose() with an if (disposing) check.
src/libraries/Common/src/System/Security/Cryptography/MLDsaImplementation.Windows.cs	Added an explicit if (disposing) check before disposing _key and then calling base.Dispose(disposing).
src/libraries/Common/src/System/Security/Cryptography/MLDsaCng.Windows.cs	Added an explicit if (disposing) check before disposing _key and then calling base.Dispose(disposing).

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.