This pull request introduces significant improvements to the PowerShell 7 engine integration, focusing on enhanced type handling between PowerShell and .NET, better compatibility with Windows PowerShell 5.1, and extended build/test automation support. The changes ensure that complex and primitive types are correctly marshaled, session and engine variables are consistently set, and development workflows are streamlined with new VSCode tasks.

PowerShell 7 Engine Improvements:

Enhanced object serialization and deserialization: The engine now outputs type information alongside property values (in the format TypeName|Key=Value), allowing the .NET side to reconstruct the original types using the new ConvertFromJSONString method. This ensures accurate handling of booleans, numbers, strings, and complex objects. [1] [2] [3] [4]
Added engine identification variables (PSMAEngineType, PSMAEngineVersion, PSMAEngineSelected) for improved compatibility and diagnostics, especially with Windows PowerShell 5.1. [1] [2]
Session variables are now injected into the PowerShell runtime when provided, increasing flexibility for script execution. [1] [2]
Type and Dependency Updates:

Added a reference to System.Runtime.Serialization in the project file to support JSON deserialization of complex types.
Updated the assembly file version to 6.0.1022.2025.
Bug Fixes:

Improved error handling in import logic to avoid false anchor errors when an error name is already set.
Other Technical Enhancements:

Added System.Runtime.Serialization.Json using directive to support new serialization logic.